Enginemailer

MARKETING · EMAIL

Subscribers, custom fields, and campaigns in the account they connected.

Connect Enginemailer with Fabriq Developer

Your user pastes their Enginemailer credential on a page Agentic Fabriq hosts, so it never reaches your backend and never becomes one shared key across all of your users. Same call as OAuth, one more argument.

from af_sdk import AgenticFabriq

af = AgenticFabriq()                      # reads AF_APP_ID / AF_APP_SECRET

url = await af.initiate_connection(request, provider="enginemailer", method="api_key")
return redirect(url)                      # an AF-hosted page, not yours

async with await af.for_user(request) as session:
    tools = await session.get_tools()     # only what this user granted

Provider names are surfaces, not vendors, and the authoritative list is the capabilities endpoint rather than any page including this one — an unknown name returns 400 with the valid list. Fabriq Developer is free to start and needs no provider paperwork. Start free or read the quickstart.

Connecting Enginemailer in practice

Enginemailer reports failures as English sentences rather than codes — "API Key Not Found", "Exceed Daily Insert Limit", "Duplicate Custom Key" — so an agent has to branch on message text, and a wording change upstream silently breaks its error handling. Version 2 and a deprecated version 1 are documented side by side for transactional send and for reporting, with Enginemailer recommending version 2 because the older one no longer receives enhancements.

Scopes that draw scrutiny

APIKey header A single account-wide key sent in a header named APIKey. Enginemailer says to include only this one authentication parameter; there is no scope model and no read-only variant.

Worth knowing

The method name is part of the path rather than a parameter: transactional send is POST https://api.enginemailer.com/RESTAPI/V2/Submission/SendEmail, so moving between versions rewrites every URL.
"Exceed Daily Insert Limit" is the only quota signal in the documented error list and no number is published for it, so the ceiling is discovered by hitting it.
The REST API accepts JSON only, and errors come back in the response body rather than as distinct HTTP status codes.
Subscriber writes have both single and batch forms — Batch Update Subscribers and Batch Update Status alongside the per-record calls — with no documented difference in limits between them.

Checked against Submitting transactional emails via REST API v2 (2026-09-29), Errors for Subscribers API (2026-09-29), Subscriber REST API reference (2026-09-29)

Acts as the person, not as itself

Each user connects their own account. Every call carries both identities — the agent and the person it is acting for — so the agent can never reach past what that individual can already do.

Credentials never touch the agent

Tokens live in the vault and attach server-side at call time. The agent holds a session, not a secret, and revoking access does not mean rotating a key.

Every call on the record

Who asked, which agent acted, which action ran, and the verdict that let it through — one audit trail across every integration, not one per vendor.

What an agent can do

Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.

enginemailer_get_restapi_campaign_emcampaign_deletecampaignWRITE

Delete Campaign via GET /restapi/campaign/emcampaign/DeleteCampaign. Deleting undelivered campaign. Please note of the following before starting use this function Scheduled, delivering, delivered campaign is not able to perform the deleting. This function will not work when the campaign is inserting / deleting the recipient list. Paid plans only: "The campaign API only allow the PAID user to use the service." (https://enginemailer.zendesk.com/hc/en-us/articles/360003129972-Campaign-REST-API-GETTING-STARTED). A Free account receives "Free account is not eligible to use API!" (https://enginemailer.zendesk.com/hc/en-us/articles/360003892652-Errors-for-Campaign-API).

api

enginemailer_get_restapi_campaign_emcampaign_deleterecipientlistWRITE

Delete Recipient List via GET /restapi/campaign/emcampaign/deleteRecipientList. Delete existing recipient list from the targeted campaign. Please note of the following before starting use this function Scheduled, delivering, delivered campaign is not able to perform the deleting. This function will not work when the campaign is inserting / deleting the recipient list. Paid plans only: "The campaign API only allow the PAID user to use the service." (https://enginemailer.zendesk.com/hc/en-us/articles/360003129972-Campaign-REST-API-GETTING-STARTED). A Free account receives "Free account is not eligible to use API!" (https://enginemailer.zendesk.com/hc/en-us/articles/360003892652-Errors-for-Campaign-API).

api

enginemailer_get_restapi_campaign_emcampaign_getcategorylistREAD

Get Category List via GET /restapi/campaign/emcampaign/GetCategoryList. Get a list of category. No parameter is required Paid plans only: "The campaign API only allow the PAID user to use the service." (https://enginemailer.zendesk.com/hc/en-us/articles/360003129972-Campaign-REST-API-GETTING-STARTED). A Free account receives "Free account is not eligible to use API!" (https://enginemailer.zendesk.com/hc/en-us/articles/360003892652-Errors-for-Campaign-API).

api

enginemailer_get_restapi_campaign_emcampaign_getsubcategorylistREAD

Get Sub Category List via GET /restapi/campaign/emcampaign/GetSubCategoryList. Get a list of subcategory based on the category ID Paid plans only: "The campaign API only allow the PAID user to use the service." (https://enginemailer.zendesk.com/hc/en-us/articles/360003129972-Campaign-REST-API-GETTING-STARTED). A Free account receives "Free account is not eligible to use API!" (https://enginemailer.zendesk.com/hc/en-us/articles/360003892652-Errors-for-Campaign-API).

api

enginemailer_get_restapi_campaign_emcampaign_listcampaignREAD

List Campaign via GET /restapi/campaign/emcampaign/ListCampaign. Get a list of undelivered campaigns. No parameter is required Paid plans only: "The campaign API only allow the PAID user to use the service." (https://enginemailer.zendesk.com/hc/en-us/articles/360003129972-Campaign-REST-API-GETTING-STARTED). A Free account receives "Free account is not eligible to use API!" (https://enginemailer.zendesk.com/hc/en-us/articles/360003892652-Errors-for-Campaign-API).

api

enginemailer_get_restapi_campaign_emcampaign_pausecampaignWRITE

Pause Campaign via GET /restapi/campaign/emcampaign/PauseCampaign. Pause the campaign from a scheduled campaign. Please note of the following before starting use this function Only scheduled without delivering campaign is able to perform the pause for the campaign Paid plans only: "The campaign API only allow the PAID user to use the service." (https://enginemailer.zendesk.com/hc/en-us/articles/360003129972-Campaign-REST-API-GETTING-STARTED). A Free account receives "Free account is not eligible to use API!" (https://enginemailer.zendesk.com/hc/en-us/articles/360003892652-Errors-for-Campaign-API).

api

enginemailer_get_restapi_campaign_emcampaign_schedulecampaignWRITE

Schedule Campaign via GET /restapi/campaign/emcampaign/ScheduleCampaign. Schedule the campaign. Please note of the following before starting use this function Scheduled, delivering, delivered campaign is not able to perform the scheduling. This function will not work when the campaign is deleting the recipient list. The campaign must at least have one recipient to deliver the campaign. Schedule Date must not be a passed date. Schedule Date must follow the standard of scheduling in the portal. It must be in the interval of 15 minutes. For g., 12:00, 12:15, 12:30, 12:45, others format of the schedule time will be rejected. Insufficient credit will flag the scheduled campaign as “failed” and campaign will not send at the scheduled time. Failed campaign can be edited and resend from the portal. Paid plans only: "The campaign API only allow the PAID user to use the service." (https://enginemailer.zendesk.com/hc/en-us/articles/360003129972-Campaign-REST-API-GETTING-STARTED). A Free account receives "Free account is not eligible to use API!" (https://enginemailer.zendesk.com/hc/en-us/articles/360003892652-Errors-for-Campaign-API).

api

enginemailer_get_restapi_campaign_emcampaign_sendcampaignWRITE

Send Campaign via GET /restapi/campaign/emcampaign/SendCampaign. Send the campaign. Please note of the following before starting use this function Scheduled, delivering, delivered campaign is not able to perform the sending. This function will not work when the campaign is deleting the recipient list. The campaign must at least have one recipient to deliver the campaign. Paid plans only: "The campaign API only allow the PAID user to use the service." (https://enginemailer.zendesk.com/hc/en-us/articles/360003129972-Campaign-REST-API-GETTING-STARTED). A Free account receives "Free account is not eligible to use API!" (https://enginemailer.zendesk.com/hc/en-us/articles/360003892652-Errors-for-Campaign-API).

api

enginemailer_get_restapi_subscriber_emsubscriber_getcustomfieldREAD

Get Custom Field via GET /restapi/subscriber/emsubscriber/getCustomField. Get Custom Field List.

api

enginemailer_get_restapi_subscriber_emsubscriber_getsubcategoryREAD

Get Sub Category via GET /restapi/subscriber/emsubscriber/getSubCategory. Get Sub Category List.

api

enginemailer_get_restapi_subscriber_emsubscriber_getsubscriberREAD

Get Subscriber via GET /restapi/subscriber/emsubscriber/getSubscriber. Get information about a subscriber.

api

enginemailer_get_restapi_subscriber_emsubscriber_unsubsubscriberWRITE

UnSub Subscriber via GET /restapi/subscriber/emsubscriber/unSubSubscriber. Unsubscribe existing subscriber from subscriber list.

api

enginemailer_post_restapi_campaign_emcampaign_assignrecipientlistWRITE

Assign Recipient List via POST /restapi/campaign/emcampaign/AssignRecipientList. Assign recipient list to the targeted campaign. Please note of the following before starting use this function Scheduled, delivering, delivered campaign is not able to perform the assigning. This function will not work when the campaign is inserting / deleting the recipient list. The subcategoryid please get from the function which named as getSubCategoryList. Paid plans only: "The campaign API only allow the PAID user to use the service." (https://enginemailer.zendesk.com/hc/en-us/articles/360003129972-Campaign-REST-API-GETTING-STARTED). A Free account receives "Free account is not eligible to use API!" (https://enginemailer.zendesk.com/hc/en-us/articles/360003892652-Errors-for-Campaign-API).

api

enginemailer_post_restapi_campaign_emcampaign_createcampaignWRITE

Create Campaign via POST /restapi/campaign/emcampaign/CreateCampaign. Creation of the campaign. Note: The user can only create campaign with the maximum number of 200. If intend to create more campaign, you are required to delete older campaigns. Paid plans only: "The campaign API only allow the PAID user to use the service." (https://enginemailer.zendesk.com/hc/en-us/articles/360003129972-Campaign-REST-API-GETTING-STARTED). A Free account receives "Free account is not eligible to use API!" (https://enginemailer.zendesk.com/hc/en-us/articles/360003892652-Errors-for-Campaign-API).

api

enginemailer_post_restapi_campaign_emcampaign_updatecampaignWRITE

Update Campaign via POST /restapi/campaign/emcampaign/UpdateCampaign. Update data for existing campaign. Paid plans only: "The campaign API only allow the PAID user to use the service." (https://enginemailer.zendesk.com/hc/en-us/articles/360003129972-Campaign-REST-API-GETTING-STARTED). A Free account receives "Free account is not eligible to use API!" (https://enginemailer.zendesk.com/hc/en-us/articles/360003892652-Errors-for-Campaign-API).

api

enginemailer_post_restapi_subscriber_emsubscriber_activatesubscriberWRITE

Activate Subscriber via POST /restapi/subscriber/emsubscriber/activateSubscriber. Activate an inactive subscriber. Only applicable to the subscriber that is deactivated either through the API or manually.

api

enginemailer_post_restapi_subscriber_emsubscriber_batchupdatestatusREAD

Batch Update Status via POST /restapi/subscriber/emsubscriber/batchUpdateStatus. Retrieve the status for the Batch Update Subscribers job, using the ID that is returned from the API.

api

enginemailer_post_restapi_subscriber_emsubscriber_batchupdatesubscribersWRITE

Batch Update Subscribers via POST /restapi/subscriber/emsubscriber/batchUpdateSubscribers. Add or Update the list of subscribers based on the custom fields and subcategories provided in the JSON data. Subscribers data that does not pass the validation will be removed from processing. Retrieve the status for the job using Batch Update Status.

api

enginemailer_post_restapi_subscriber_emsubscriber_deletesubscriberWRITE

Delete Subscriber via POST /restapi/subscriber/emsubscriber/deleteSubscriber. Delete a subscriber, identified by email. (The vendor article's own summary line reads 'Insertion of a subscriber.', copied from Insert Subscriber.).

api

enginemailer_post_restapi_subscriber_emsubscriber_insertsubscriberWRITE

Insert Subscriber via POST /restapi/subscriber/emsubscriber/insertSubscriber. Insertion of a subscriber. Note: The user can only insert with the maximum number of 50/day with the free account and 10,000/day with the paid account.

api

enginemailer_post_restapi_subscriber_emsubscriber_updatecategoryWRITE

Create Update Category via POST /restapi/subscriber/emsubscriber/updateCategory. Create or modify the category and subcategories using the data provided in JSON format.

api

enginemailer_post_restapi_subscriber_emsubscriber_updatesubscriberWRITE

Update Subscriber via POST /restapi/subscriber/emsubscriber/updateSubscriber. Update data for an existing subscriber.

api

enginemailer_post_restapi_v2_submission_report_checkexportREAD

Check Export Status Version 2 via POST /RESTAPI/V2/Submission/Report/CheckExport. You can export transactional email reports using API. Once you've initiated the export using this method, it will undergo a processing phase which may take some time to complete. Check Export Status Go to https://api.enginemailer.com/RESTAPI/V2/Submission/Report/CheckExport and use the ExportID that you received from the Export method to check the status. Please note that our REST API only accepts JSON object as a parameter list. To ensure proper authentication, you should include only one authentication parameter (APIKey) within the header. Below is an example of the response. If the export is still processing, it will display a "Processing" status. If the export is complete, it will display a "Complete" status and the URL to download the file.

api

enginemailer_post_restapi_v2_submission_report_exportWRITE

Export CSV Report Version 2 via POST /RESTAPI/V2/Submission/Report/Export. You can export transactional email reports using API at this link: Please note that our REST API only accepts JSON object as a parameter list. To ensure proper authentication, you should include only one authentication parameter (APIKey) within the header. Below is an example of the response. Use the ExportID to check for the export status in here.

api

enginemailer_post_restapi_v2_submission_sendemailWRITE

Submitting Transactional Emails via REST-API Version 2 via POST /RESTAPI/V2/Submission/SendEmail. We recommend that you use this version as the previous version will no longer be updated for new enhancements. You can submit emails by invoking the Enginemailer Email Service at https://api.enginemailer.com/RESTAPI/V2/Submission/SendEmail Please note that our REST API only accepts JSON object as a parameter list. To ensure proper authentication, you should include only one authentication parameter (APIKey) within the header. We allow users to send emails with or without templates. To create a template, please visit here.

api

Often connected alongside

Put Enginemailer behind one governed endpoint.

Same permissions, same audit trail, whatever else you connect next.

Start free See pricing