an optional description of why the email was added to the allowlist

an optional email address or prefix to search by.

the email address to remove from the allowlist.

an optional email address to notify when the export job has finished.

an array of api keys to narrow the export to; messsagse sent with ANY of the keys will be included.

start date as a UTC string in YYYY-MM-DD HH

end date as a UTC string in YYYY-MM-DD HH

an optional email address to notify when the export job has finished

an array of senders to narrow the export to

an array of message states to narrow the export to; messages with ANY of the states will be included

the id of the pool to add the dedicated ip to

whether to create the pool if it does not exist; if false and the pool does not exist an Unknown_Pool will be thrown.

the name of the new pool to add the dedicated ip to

the dedicated ip to remove from your account

a domain name to set as the dedicated IP's custom dns name.

List the domains that have been configured for inbound delivery

Check the MX settings for an inbound domain

Delete an inbound domain from the account

List the mailbox routes defined for an inbound domain

Add a new mailbox route to an inbound domain

the search pattern that the mailbox name should match

the webhook URL where the inbound messages will be published.

Update the pattern or webhook of an existing inbound mailbox route

the unique identifier of an existing mailbox route

the unique identifier of an existing route.

Take a raw MIME document destined for a domain with inbound domains set up, and send it to the inbound hook exactly as if it had been sent over SMTP

the identification provided by the client mta in the MTA state of the SMTP conversation

the address specified in the MAIL FROM stage of the SMTP conversation. Required for the SPF check

the full MIME document of an email message

optionally define the recipients to receive the message - otherwise we'll use the To Cc and Bcc headers provided in the document

Send a new transactional message through the Transactional API

Enable a background sending mode that is optimized for bulk sending

Send a new transactional message through the Transactional API using a template

enable a background sending mode that is optimized for bulk sending.

the name of the dedicated ip pool that should be used to send the message

the other information on the message to send - same as /messages/send but without the html content

when this message should be sent as a UTC timestamp

the immutable name or slug of a template that exists in the user's account

an array of API keys to narrow the search to will return messages sent by ANY of the keys

the maximum number of results to return defaults to 100 1000 is the maximum.

an array of sender addresses to narrow the search to will return messages sent by ANY of the senders

Search the content of recently sent messages and return the aggregated hourly stats for matching messages

the search terms to find matching messages for

Get the information for a single recently sent message

the unique id of the message to get - passed as the "_id" field in webhooks send calls or search calls.

Get the full content of a recently sent message

Parse the full MIME document for an email message, returning the content of the message broken into its constituent pieces

the full MIME document of an email message.

Take a raw MIME document for a message, and send it exactly as if it were sent through the Transactional API's SMTP servers

enable a background sending mode that is optimized for bulk sending

optionally define the sender address - otherwise we'll use the address found in the provided headers

a custom domain to use for the messages's return-path.

optionally define the recipient to receive the message - otherwise we'll use the To Cc and Bcc headers provided in the document

an optional recipient address to restrict results to

a scheduled email id as returned by any of the messages/send calls or messages/list-scheduled.

a scheduled email id as returned by any of the messages/send calls or messages/list-scheduled

the new UTC timestamp when the message should sent.

an optional comment describing the rejection

an optional unique identifier for the subaccount to limit the denylist entry.

whether to include rejections that have already expired

an optional unique identifier for the subaccount to limit the denylist

an optional unique identifier for the subaccount to limit the denylist deletion.

domain name at which you can receive email

a mailbox at the domain where the verification email should be sent.

an optional prefix to filter the subaccounts' ids and names.

an optional manual hourly quota for the subaccount. If not specified Mandrill will manage this based on reputation.

a unique identifier for the subaccount to be used in sending calls

an optional display name to further identify the subaccount

optional extra text to associate with the subaccount

the unique identifier of the subaccount to query.

an optional manual hourly quota for the subaccount

the unique identifier of the subaccount to update

the unique identifier of the subaccount to delete.

the unique identifier of the subaccount to pause.

the unique identifier of the subaccount to resume.

a default sending address for emails sent using this template

an optional array of up to 10 labels to use for filtering templates.

the name for the new template - must be unique

set to false to add a draft template without publishing

a default text part to be used when sending with this template

the immutable name of an existing template

set to false to update the draft version of the template without publishing

the immutable name of an existing template.

an optional label to filter the templates.

the immutable name of a template that exists in the user's account

Get the list of tracking domains set up for this account

an optional list of events that will be posted to the webhook.

the unique identifier of a webhook belonging to this account.

the unique identifier of a webhook belonging to this account

the URL to POST batches of events. Requires webhook to exist

Mailchimp

Mailchimp API

Pre-configured, Predictable, Single Interface, Ready-to-use, Opinionated & Managed API Explorer & Server. Bring your API credentials, configure and access your 3rd party APIs. Using LowCodeAPI securely manage all integrations in one place.