Skip to content
Changelog

Report a bug

Enginemailer integration: operations for AI agents

Enginemailer connects to Type.com as an integration. This page lists the 30 operations documented for Claude and Codex in Type.com: 11 read, 12 write, 7 destructive.

About Enginemailer

Enginemailer vendor API references, subject to account permissions.

Categories: Marketing & Social

How to connect Enginemailer to Type.com

Access
Organization connection: one shared account for the workspace.

To add the connection, follow the steps in Space connections.

Documented operations

30 operations. Your connection's permissions determine which operations are available. API references describe the vendor surface; they do not expand your connection's credentials or access.

30 operations listed.

Campaign

  • Read

    Get Campaign Delivery Status

    GetCampaignDeliveryStatus Retrieve summary delivery and engagement statistics for a delivered campaign.

    GET /restapi/campaign/emcampaign/getcampaigndeliverystatus

  • Read

    Get Category List

    GetCategoryList Get a list of category. No parameter is required

    GET /restapi/campaign/emcampaign/GetCategoryList

  • Read

    Get Sub Category List

    GetSubCategoryList Get a list of subcategory based on the category ID

    GET /restapi/campaign/emcampaign/GetSubCategoryList

  • Read

    List Campaign

    ListCampaign Get a list of undelivered campaigns. No parameter is required

    GET /restapi/campaign/emcampaign/ListCampaign

  • Write

    Create Campaign

    CreateCampaign Creation of the campaign.

    POST /restapi/Campaign/EMCampaign/CreateCampaign

  • Write

    Update Campaign

    Updates existing campaign content and required campaign fields; omission or array replacement semantics are not inferred. Source table incorrectly labels CampaignName/SenderName as array types while its example uses strings; unresolved source conflict preserved.

    POST /restapi/Campaign/EMCampaign/UpdateCampaign

  • Write

    Assign Recipient List

    AssignRecipientList Assign recipient list to the targeted campaign.

    POST /restapi/campaign/emcampaign/AssignRecipientList

  • Write

    Send Campaign

    Starts sending an existing campaign; vendor implements this state-changing action as GET.

    GET /restapi/campaign/emcampaign/SendCampaign

  • Write

    Schedule Campaign

    Schedules an existing campaign for sending; vendor implements this state-changing action as GET.

    GET /restapi/campaign/emcampaign/ScheduleCampaign

  • Destructive

    Delete Campaign

    Deletes the existing campaign; vendor implements this as GET.

    GET /restapi/campaign/emcampaign/deletecampaign

  • Destructive

    Delete Recipient List

    Deletes the existing recipient list for a campaign, not the subscriber database. Scheduled/delivering/delivered campaigns cannot use this operation; GET mutates.

    GET /restapi/campaign/emcampaign/deleteRecipientList

  • Destructive

    Pause Campaign

    Pauses the existing campaign; vendor implements this as GET.

    GET /restapi/campaign/emcampaign/PauseCampaign

Subscribers

  • Read

    Get Subscriber

    GetSubscriber Get information about a subscriber. Source URL uses an unnamed ?{email} placeholder, while code illustrates a named email query; both retained without claiming wire equivalence.

    GET /restapi/subscriber/emsubscriber/getSubscriber

  • Read

    Get Sub Category

    GetSubCategory Get Sub Category List.

    GET /restapi/subscriber/emsubscriber/getSubCategory

  • Read

    Get Custom Field

    GetCustomField Get Custom Field List. Source HTTP method says GET, but .NET example uses Method.POST; linked PHP example supports GET. Preserve this conflict rather than declaring both equivalent.

    GET /restapi/subscriber/emsubscriber/getCustomField

  • Read

    Batch Update Status

    Retrieves the status of an existing batch subscriber job. POST is semantic read; body StatusCode fields are not proof of the transport HTTP status.

    POST /restapi/subscriber/emsubscriber/batchUpdateStatus

  • Write

    Activate Subscriber

    ActivateSubscriber Activate an inactive subscriber. Only applicable to the subscriber that is deactivated either through the API or manually. Source URL uses an unnamed ?{email} placeholder, while code illustrates a named email query; both retained without claiming wire equivalence.

    POST /restapi/subscriber/emsubscriber/activateSubscriber

  • Write

    Insert Subscriber

    InsertSubscriber Insertion of a subscriber.

    POST /restapi/subscriber/emsubscriber/insertSubscriber

  • Write

    Batch Update Subscribers

    Adds or updates up to 5,000 subscribers in an asynchronous batch. Invalid records are removed from processing, not asserted deleted from the subscriber database.

    POST /restapi/subscriber/emsubscriber/batchUpdateSubscribers

  • Destructive

    Update Subscriber

    Conditional: SubCategories_type=2 deletes supplied category associations, =3 replaces categories; customfield_type=1 replaces provided custom fields (documented default1). Exact zero/append/update semantics are retained.

    POST /restapi/subscriber/emsubscriber/updateSubscriber

  • Destructive

    UnSub Subscriber

    Unsubscribes the existing subscriber; vendor implements this as GET.

    GET /restapi/subscriber/emsubscriber/unSubSubscriber

  • Destructive

    Create Update Category

    Creates or modifies category/subcategory data; conditional isvisible=false hides the existing category. Source field casing variants/types/examples are retained.

    POST /restapi/subscriber/emsubscriber/updateCategory

  • Destructive

    Delete Subscriber

    The operation title/path identify subscriber deletion although its introductory sentence incorrectly says insertion; preserve this source conflict. POST is not read-only.

    POST /restapi/subscriber/emsubscriber/deleteSubscriber

Transactional

  • Write

    Submitting Transactional Emails via REST-API (Deprecated) (deprecated)

    Sends transactional email with the explicitly deprecated legacy route. HTTP POST is evidenced by its linked official JQuery example; body UserKey/APIKey auth wording and malformed samples are retained.

    POST /RESTAPI/Submission/SendEmail

Conflicting method example

  • Read

    Get Custom Field (.NET example conflict)

    Source .NET code uses Method.POST, conflicting with the explicit HTTP GET declaration and linked PHP GET example. This is a conflicting sample reference, not proof of equivalent endpoint support.

    POST /restapi/subscriber/emsubscriber/getCustomField

HTTP method unspecified

  • Read

    Check Export Status Version 2

    Retrieves report-export processing/complete status and output URL. The article does not explicitly state the HTTP verb.

    /RESTAPI/V2/Submission/Report/CheckExport

  • Read

    Check Export Status (Deprecated) (deprecated)

    Retrieves report-export status using a deprecated legacy route. Explicit HTTP verb is not stated.

    /RESTAPI/Submission/Report/CheckExport

  • Write

    Export CSV Report Version 2

    Starts asynchronous report export with date/email/domain filters; result ExportID is polled. Source route/payload omit an explicit HTTP verb.

    /RESTAPI/V2/Submission/Report/Export

  • Write

    Submitting Transactional Emails via REST-API Version 2

    Sends transactional email using APIKey header and JSON payload; source route/payload are complete but this article does not explicitly state the HTTP verb.

    /RESTAPI/V2/Submission/SendEmail

  • Write

    Export CSV Report (Deprecated) (deprecated)

    Starts a report export using a deprecated legacy route; explicit HTTP verb is absent from captured article.

    /RESTAPI/Submission/Report/Export

See How connections work for access and permissions, or browse all integrations.