How can we help you?

FeraEmail

Setup, administration, developer, and API documentation for FeraEmail.

FeraEmail

Create or update an email template

Implements controller.createOrUpdate in routes/api/v1/template/routes.js:8. The authenticated owner boundary enforces view/edit permission and never returns SMTP passwords; templates and profiles are isolated by instance owner.

Applies to all documented versions
FeraEmail

Create or update an SMTP configuration

Implements controller.createOrUpdate in routes/api/v1/configuration/routes.js:8. The authenticated owner boundary enforces view/edit permission and never returns SMTP passwords; templates and profiles are isolated by instance owner.

Applies to all documented versions
FeraEmail

Delete an email template

Implements controller.destroy in routes/api/v1/template/routes.js:14. The authenticated owner boundary enforces view/edit permission and never returns SMTP passwords; templates and profiles are isolated by instance owner.

Applies to all documented versions
FeraEmail

Delete an SMTP configuration

Implements controller.destroy in routes/api/v1/configuration/routes.js:11. The authenticated owner boundary enforces view/edit permission and never returns SMTP passwords; templates and profiles are isolated by instance owner.

Applies to all documented versions
FeraEmail

List email templates

Implements controller.get in routes/api/v1/template/routes.js:12. The authenticated owner boundary enforces view/edit permission and never returns SMTP passwords; templates and profiles are isolated by instance owner.

Applies to all documented versions
FeraEmail

List global email templates

Implements controller.global in routes/api/v1/template/routes.js:11. The authenticated owner boundary enforces view/edit permission and never returns SMTP passwords; templates and profiles are isolated by instance owner.

Applies to all documented versions
FeraEmail

List SMTP configurations

Implements controller.get in routes/api/v1/configuration/routes.js:9. The authenticated owner boundary enforces view/edit permission and never returns SMTP passwords; templates and profiles are isolated by instance owner.

Applies to all documented versions
FeraEmail

Provision the shared FeraSign email owner

Implements inline handler in routes/api/v1/internal/signature-owner.js:7. The authenticated internal operation idempotently reconciles the shared FeraSign owner SMTP profile and templates without replacing valid credentials.

Applies to all documented versions
FeraEmail

Receive a FeraEmail lifecycle acknowledgment

FeraEmail directly posts one exact-body HMAC callback after lifecycle success or failure. There is no internal retry loop; a failed success callback fails the source request so FeraHooks can redeliver the idempotent…

Applies to all documented versions
FeraEmail

Register an email template

Implements controller.register in routes/api/v1/template/routes.js:9. The authenticated owner boundary enforces view/edit permission and never returns SMTP passwords; templates and profiles are isolated by instance owner.

Applies to all documented versions
FeraEmail

Retrieve an email template

Implements controller.get in routes/api/v1/template/routes.js:13. The authenticated owner boundary enforces view/edit permission and never returns SMTP passwords; templates and profiles are isolated by instance owner.

Applies to all documented versions
FeraEmail

Retrieve an SMTP configuration by name

Implements controller.get in routes/api/v1/configuration/routes.js:10. The authenticated owner boundary enforces view/edit permission and never returns SMTP passwords; templates and profiles are isolated by instance owner.

Applies to all documented versions
FeraEmail

Search email templates

Implements controller.search in routes/api/v1/template/routes.js:10. The authenticated owner boundary enforces view/edit permission and never returns SMTP passwords; templates and profiles are isolated by instance owner.

Applies to all documented versions
FeraEmail

Send an email

Implements controller.send in routes/api/v1/send/routes.js:8. The authenticated sender requires SEND.EMAIL, resolves an owner-scoped SMTP profile and optional template, builds safe rendered output, appends campaign opt-out once, submits through Nodemailer, records success, and never…

Applies to all documented versions
FeraEmail

The Attachment object

Source-supported Attachment schema for FeraEmail integrations.

Applies to all documented versions
FeraEmail

The EmailConfiguration object

Source-supported EmailConfiguration schema for FeraEmail integrations.

Applies to all documented versions
FeraEmail

The EmailError object

Source-supported EmailError schema for FeraEmail integrations.

Applies to all documented versions
FeraEmail

The EmailResult object

Source-supported EmailResult schema for FeraEmail integrations.

Applies to all documented versions
FeraEmail

The EmailTemplate object

Source-supported EmailTemplate schema for FeraEmail integrations.

Applies to all documented versions
FeraEmail

The LifecycleAcknowledgment object

Source-supported LifecycleAcknowledgment schema for FeraEmail integrations.

Applies to all documented versions
FeraEmail

The LifecycleEvent object

Source-supported LifecycleEvent schema for FeraEmail integrations.

Applies to all documented versions
FeraEmail

The SendRequest object

Source-supported SendRequest schema for FeraEmail integrations.

Applies to all documented versions
FeraEmail

The SendResult object

Source-supported SendResult schema for FeraEmail integrations.

Applies to all documented versions