All integrations

MailerSend

MESSAGING · MESSAGING

Transactional and bulk email, sending domains, and delivery activity on their key.

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.

mailersend_delete_domains_by_domain_idWRITE

Delete a domain. A sending domain is what authorises MailerSend to send `from` an address; a domain that is not verified cannot send.

domains_full
mailersend_delete_domains_by_domain_id_smtp_users_by_smtp_user_idWRITE

Delete SMTP user. An SMTP user is a per-domain credential for sending over SMTP rather than the API.

smtp_users_full
mailersend_delete_identities_by_identity_idWRITE

Delete a sender identity. A sender identity authorises ONE address on a domain to send, which is how an account sends `from` an address it has not verified the whole domain for.

sender_identity_full
mailersend_delete_identities_email_emailWRITE

Delete a sender identity by Email. A sender identity authorises ONE address on a domain to send, which is how an account sends `from` an address it has not verified the whole domain for.

sender_identity_full
mailersend_delete_inbound_by_inbound_idWRITE

Delete an inbound route. An inbound route receives mail sent TO a subdomain you control and forwards it to a webhook or an address.

inbounds_full
mailersend_delete_message_schedules_by_message_idWRITE

Delete a scheduled message. A scheduled message is a send whose `send_at` is in the future; it can be inspected and cancelled until it is delivered.

email_full
mailersend_delete_recipients_by_recipient_idWRITE

Delete a recipient. A recipient is an address MailerSend has seen on this account, with its suppression state.

recipients_full
mailersend_delete_sms_inbounds_by_sms_inbound_idWRITE

Delete an SMS inbound route. An SMS inbound route forwards received texts to a URL.

sms_full
mailersend_delete_sms_numbers_by_sms_number_idWRITE

Delete an SMS phone number. Phone numbers are purchased in the MailerSend dashboard, not through the API.

sms_full
mailersend_delete_sms_webhooks_by_sms_webhook_idWRITE

Delete an SMS webhook. An SMS webhook delivers SMS events to a URL you control. Sends NO body, on the SAME CONTRACT-DEFECT basis, and here it is worse: the contract declares `{"enabled": boolean}` REQUIRED, verbatim the request body of the PUT on the same path, so shipping it would make an agent supply `enabled` in order to DELETE a webhook. NOT MEASURED -- the trial account's 100-request daily budget ran out before an SMS webhook could be created and deleted. Nothing about the account prevents it: it does hold an SMS phone number (3z0vkloq6j147qrx, seen 2026-09-19), so this is measurable whenever budget allows.

sms_full
mailersend_delete_suppressions_blocklistWRITE

Delete recipients from the blocklist suppression list. A suppression list blocks delivery to an address. MailerSend keeps four of them -- blocklist, hard bounces, spam complaints, unsubscribes -- and they are per DOMAIN.

suppressions_full
mailersend_delete_suppressions_hard_bouncesWRITE

Delete recipients from the hard bounces suppression list. A suppression list blocks delivery to an address. MailerSend keeps four of them -- blocklist, hard bounces, spam complaints, unsubscribes -- and they are per DOMAIN.

suppressions_full
mailersend_delete_suppressions_spam_complaintsWRITE

Delete recipients from the spam complaints suppression list. A suppression list blocks delivery to an address. MailerSend keeps four of them -- blocklist, hard bounces, spam complaints, unsubscribes -- and they are per DOMAIN.

suppressions_full
mailersend_delete_suppressions_unsubscribesWRITE

Delete recipients from the unsubscribes suppression list. A suppression list blocks delivery to an address. MailerSend keeps four of them -- blocklist, hard bounces, spam complaints, unsubscribes -- and they are per DOMAIN.

suppressions_full
mailersend_delete_token_by_token_idWRITE

Delete a token. These manage MailerSend API TOKENS -- the same kind of credential this connection itself holds. The connection's own token must carry API tokens = Full access, and a created token's secret is returned ONCE, in the create response.

tokens_full
mailersend_delete_users_by_user_idWRITE

Delete a user. Users are the people with access to the MailerSend account, and their roles.

users_full
mailersend_delete_webhooks_by_webhook_idWRITE

Delete a webhook. A webhook delivers email events to a URL you control; it belongs to one domain, which is why listing them REQUIRES `domain_id`. Sends NO body, and the BASIS IS A CONTRACT DEFECT rather than a measurement -- which matters, because it decides whether this can be restored by re-reading the contract or only by re-measuring. MailerSend's OpenAPI declares `{"enabled": boolean}` on this DELETE, and that is verbatim the request body of the PUT on the same path: the update's payload copied onto the delete. Deleting a webhook takes no payload. NOT MEASURED -- the trial account's daily request budget ran out before the webhook created for the purpose could be deleted; docs/integrations/mailersend/verified.json records this tool as untested.

webhooks_full
mailersend_get_activities_by_activity_idREAD

Get single activity. Activity is the per-recipient delivery event log for a sending domain (queued, sent, delivered, soft/hard bounced, opened, clicked, unsubscribed, spam complaint). `date_from` and `date_to` are REQUIRED UTC unix timestamps.

activity_read
mailersend_get_activity_by_domain_idREAD

Get a list of activities for a domain. Activity is the per-recipient delivery event log for a sending domain (queued, sent, delivered, soft/hard bounced, opened, clicked, unsubscribed, spam complaint). `date_from` and `date_to` are REQUIRED UTC unix timestamps.

activity_read
mailersend_get_analytics_countryREAD

Opens by country. Analytics are aggregate counts over a date window rather than per-message rows; `date_from` and `date_to` are REQUIRED UTC unix timestamps and MailerSend retains six months.

analytics_read
mailersend_get_analytics_dateREAD

Activity data by date. Analytics are aggregate counts over a date window rather than per-message rows; `date_from` and `date_to` are REQUIRED UTC unix timestamps and MailerSend retains six months. ⚠ The `events` filter reaches MailerSend as `event[]`, which this integration does; the contract's own spelling is accepted with 200 and SILENTLY IGNORED (measured 2026-09-19: `?events=sent` returns stats rows with no `sent` key, `?event[]=sent` returns them with one). Ask for the event names you want -- queued, sent, delivered, soft_bounced, hard_bounced, opened, clicked, unsubscribed, spam_complaints -- and each appears as its own key on every row of `stats`.

analytics_read
mailersend_get_analytics_ua_nameREAD

Opens By User-Agent. Analytics are aggregate counts over a date window rather than per-message rows; `date_from` and `date_to` are REQUIRED UTC unix timestamps and MailerSend retains six months.

analytics_read
mailersend_get_analytics_ua_typeREAD

Opens by reading environment. Analytics are aggregate counts over a date window rather than per-message rows; `date_from` and `date_to` are REQUIRED UTC unix timestamps and MailerSend retains six months.

analytics_read
mailersend_get_api_quotaREAD

Get API quota. Reports the account's remaining daily API request allowance and when it resets. MailerSend documents this endpoint as NOT counting against the quota it reports, and it needs no token permission at all. Needs no token permission: measured 2026-09-19 it answered 200 to a token minted with `analytics_read` alone and to one minted with `templates_full` alone, while each of those answered 403 #MS40301 to the other's area. MailerSend documents requests to this endpoint as not counting against the quota they report.

api
mailersend_get_bulk_email_by_bulk_email_idREAD

Get bulk email status. Sending requires a VERIFIED sending domain -- the `from.email` address must belong to one -- and a trial account may be limited to the MailerSend-issued trial domain.

email_full
mailersend_get_domainsREAD

Get a list of domains. A sending domain is what authorises MailerSend to send `from` an address; a domain that is not verified cannot send.

domains_read
mailersend_get_domains_by_domain_idREAD

Get a single domain. A sending domain is what authorises MailerSend to send `from` an address; a domain that is not verified cannot send.

domains_read
mailersend_get_domains_by_domain_id_dns_recordsREAD

Get DNS Records. A sending domain is what authorises MailerSend to send `from` an address; a domain that is not verified cannot send.

domains_read
mailersend_get_domains_by_domain_id_recipientsREAD

Get recipients for a domain. A sending domain is what authorises MailerSend to send `from` an address; a domain that is not verified cannot send.

domains_read
mailersend_get_domains_by_domain_id_smtp_usersREAD

Get a list of SMTP users. An SMTP user is a per-domain credential for sending over SMTP rather than the API.

smtp_users_read
mailersend_get_domains_by_domain_id_smtp_users_by_smtp_user_idREAD

Get a single SMTP user. An SMTP user is a per-domain credential for sending over SMTP rather than the API.

smtp_users_read
mailersend_get_domains_by_domain_id_verifyREAD

Get verification status. A sending domain is what authorises MailerSend to send `from` an address; a domain that is not verified cannot send.

domains_read
mailersend_get_email_verificationREAD

Get all lists. Email verification checks whether an address is deliverable before you send to it; a list is created, then verified, then its results are read.

email_verification_read
mailersend_get_email_verification_by_email_verification_idREAD

Get a single list. Email verification checks whether an address is deliverable before you send to it; a list is created, then verified, then its results are read.

email_verification_read
mailersend_get_email_verification_by_email_verification_id_resultsREAD

Get list results. Email verification checks whether an address is deliverable before you send to it; a list is created, then verified, then its results are read.

email_verification_read
mailersend_get_email_verification_by_email_verification_id_verifyREAD

Verify a list. Email verification checks whether an address is deliverable before you send to it; a list is created, then verified, then its results are read.

email_verification_read
mailersend_get_identitiesREAD

Get a list of sender identities. A sender identity authorises ONE address on a domain to send, which is how an account sends `from` an address it has not verified the whole domain for.

sender_identity_read
mailersend_get_identities_by_identity_idREAD

Get a single sender identity. A sender identity authorises ONE address on a domain to send, which is how an account sends `from` an address it has not verified the whole domain for.

sender_identity_read
mailersend_get_identities_email_emailREAD

Get a single sender identity by Email. A sender identity authorises ONE address on a domain to send, which is how an account sends `from` an address it has not verified the whole domain for.

sender_identity_read
mailersend_get_inboundREAD

Get a list of inbound routes. An inbound route receives mail sent TO a subdomain you control and forwards it to a webhook or an address.

inbounds_full
mailersend_get_inbound_by_inbound_idREAD

Get a single inbound route. An inbound route receives mail sent TO a subdomain you control and forwards it to a webhook or an address.

inbounds_full
mailersend_get_message_schedulesREAD

Get list of scheduled messages. A scheduled message is a send whose `send_at` is in the future; it can be inspected and cancelled until it is delivered.

email_full
mailersend_get_message_schedules_by_message_idREAD

Get a single scheduled message. A scheduled message is a send whose `send_at` is in the future; it can be inspected and cancelled until it is delivered.

email_full
mailersend_get_messagesREAD

Get a list of messages. A message is one API send request and the recipients it produced; the list is the account's recent sends.

email_full
mailersend_get_messages_by_message_idREAD

Get information for a single message. A message is one API send request and the recipients it produced; the list is the account's recent sends.

email_full
mailersend_get_recipientsREAD

Get recipients. A recipient is an address MailerSend has seen on this account, with its suppression state.

recipients_read
mailersend_get_recipients_by_recipient_idREAD

Get a single recipient. A recipient is an address MailerSend has seen on this account, with its suppression state.

recipients_read
mailersend_get_sms_activityREAD

Get a list of SMS activities. SMS activity is the per-message delivery event log.

sms_read
mailersend_get_sms_activity_by_sms_message_idREAD

Get activity of a single SMS message. SMS activity is the per-message delivery event log.

sms_read
mailersend_get_sms_inboundsREAD

Get a list of SMS inbound routes. An SMS inbound route forwards received texts to a URL.

sms_read
mailersend_get_sms_inbounds_by_sms_inbound_idREAD

Get a single SMS inbound route. An SMS inbound route forwards received texts to a URL.

sms_read
mailersend_get_sms_messagesREAD

Get a list of SMS messages. An SMS message is one send request and the recipients it produced.

sms_read
mailersend_get_sms_messages_by_sms_message_idREAD

Get an SMS message. An SMS message is one send request and the recipients it produced.

sms_read
mailersend_get_sms_numbersREAD

Get a list of SMS phone numbers. Phone numbers are purchased in the MailerSend dashboard, not through the API.

sms_read
mailersend_get_sms_numbers_by_sms_number_idREAD

Get an SMS phone number. Phone numbers are purchased in the MailerSend dashboard, not through the API.

sms_read
mailersend_get_sms_recipientsREAD

Get a list of SMS recipients. An SMS recipient is a number MailerSend has seen, with its opt-in state.

sms_read
mailersend_get_sms_recipients_by_sms_recipient_idREAD

Get an SMS recipient. An SMS recipient is a number MailerSend has seen, with its opt-in state.

sms_read
mailersend_get_sms_webhooksREAD

Get a list of SMS webhooks. An SMS webhook delivers SMS events to a URL you control.

sms_read
mailersend_get_sms_webhooks_by_sms_webhook_idREAD

Get a single SMS webhook. An SMS webhook delivers SMS events to a URL you control.

sms_read
mailersend_get_suppressions_blocklistREAD

Get recipients from the blocklist suppression list. A suppression list blocks delivery to an address. MailerSend keeps four of them -- blocklist, hard bounces, spam complaints, unsubscribes -- and they are per DOMAIN.

suppressions_read
mailersend_get_suppressions_hard_bouncesREAD

Get recipients from the hard bounces suppression list. A suppression list blocks delivery to an address. MailerSend keeps four of them -- blocklist, hard bounces, spam complaints, unsubscribes -- and they are per DOMAIN.

suppressions_read
mailersend_get_suppressions_spam_complaintsREAD

Get recipients from the spam complaints suppression list. A suppression list blocks delivery to an address. MailerSend keeps four of them -- blocklist, hard bounces, spam complaints, unsubscribes -- and they are per DOMAIN.

suppressions_read
mailersend_get_suppressions_unsubscribesREAD

Get recipients from the unsubscribes suppression list. A suppression list blocks delivery to an address. MailerSend keeps four of them -- blocklist, hard bounces, spam complaints, unsubscribes -- and they are per DOMAIN.

suppressions_read
mailersend_get_templatesREAD

Get templates. Templates are built in the MailerSend dashboard; the API lists and deletes them.

templates_full
mailersend_get_usersREAD

Get all users. Users are the people with access to the MailerSend account, and their roles.

users_read
mailersend_get_users_by_user_idREAD

Get one user. Users are the people with access to the MailerSend account, and their roles.

users_read
mailersend_get_webhooksREAD

Get a list of webhooks. A webhook delivers email events to a URL you control; it belongs to one domain, which is why listing them REQUIRES `domain_id`.

webhooks_full
mailersend_get_webhooks_by_webhook_idREAD

Get a webhook. A webhook delivers email events to a URL you control; it belongs to one domain, which is why listing them REQUIRES `domain_id`.

webhooks_full
mailersend_post_bulk_emailWRITE

Send bulk emails. Sending requires a VERIFIED sending domain -- the `from.email` address must belong to one -- and a trial account may be limited to the MailerSend-issued trial domain.

email_full
mailersend_post_domainsWRITE

Add a Domain. A sending domain is what authorises MailerSend to send `from` an address; a domain that is not verified cannot send.

domains_full
mailersend_post_emailWRITE

Send an email. Sending requires a VERIFIED sending domain -- the `from.email` address must belong to one -- and a trial account may be limited to the MailerSend-issued trial domain.

email_full
mailersend_post_email_verificationWRITE

Create a list. Email verification checks whether an address is deliverable before you send to it; a list is created, then verified, then its results are read.

email_verification_full
mailersend_post_email_verification_verifyWRITE

Verify an email. Email verification checks whether an address is deliverable before you send to it; a list is created, then verified, then its results are read.

email_verification_full
mailersend_post_identitiesWRITE

Add a sender identity. A sender identity authorises ONE address on a domain to send, which is how an account sends `from` an address it has not verified the whole domain for.

sender_identity_full
mailersend_post_inboundWRITE

Add an inbound route. An inbound route receives mail sent TO a subdomain you control and forwards it to a webhook or an address. ⚠ A `forwards` ENTRY OF TYPE `webhook` IS PROBED THE SAME WAY. Measured 2026-09-19: a route forwarding to https://example.com/... answered 422 `forwards.0.value: The endpoint returned HTTP 405.`, naming the exact element of the array that failed. The destination must answer POST.

inbounds_full
mailersend_post_smsWRITE

Send an SMS. SMS requires an SMS-enabled MailerSend plan and a phone number on the account.

sms_full
mailersend_post_sms_inboundsWRITE

Add an SMS inbound route. An SMS inbound route forwards received texts to a URL.

sms_full
mailersend_post_sms_webhooksWRITE

Create an SMS webhook. An SMS webhook delivers SMS events to a URL you control.

sms_full
mailersend_post_suppressions_blocklistWRITE

Add recipients to the blocklist suppression list. A suppression list blocks delivery to an address. MailerSend keeps four of them -- blocklist, hard bounces, spam complaints, unsubscribes -- and they are per DOMAIN.

suppressions_full
mailersend_post_suppressions_hard_bouncesWRITE

Add recipients to the hard bounces suppression list. A suppression list blocks delivery to an address. MailerSend keeps four of them -- blocklist, hard bounces, spam complaints, unsubscribes -- and they are per DOMAIN.

suppressions_full
mailersend_post_suppressions_spam_complaintsWRITE

Add recipients to the spam complaints suppression list. A suppression list blocks delivery to an address. MailerSend keeps four of them -- blocklist, hard bounces, spam complaints, unsubscribes -- and they are per DOMAIN.

suppressions_full
mailersend_post_suppressions_unsubscribesWRITE

Add recipients to the unsubscribes suppression list. A suppression list blocks delivery to an address. MailerSend keeps four of them -- blocklist, hard bounces, spam complaints, unsubscribes -- and they are per DOMAIN.

suppressions_full
mailersend_post_tokenWRITE

Create a token. These manage MailerSend API TOKENS -- the same kind of credential this connection itself holds. The connection's own token must carry API tokens = Full access, and a created token's secret is returned ONCE, in the create response. ⚠ THE RESPONSE CARRIES A LIVE CREDENTIAL. `data.accessToken` is a new MailerSend API token, shown once and never again, with whatever permissions `scopes` asked for. Treat the result as a secret. ⚠ AND A TOKEN CREATED WITHOUT AN EXPIRY DIES IN 24 HOURS: MailerSend's own help page says so, and the create response confirms there is nothing to read back -- measured 2026-09-19, a token minted through this route came back with `expires_at: null`. The API exposes no expiry field, so a token that must outlive a day has to be minted in the dashboard.

tokens_full
mailersend_post_usersWRITE

Add an user. Users are the people with access to the MailerSend account, and their roles.

users_full
mailersend_post_webhooksWRITE

Create a webhook. A webhook delivers email events to a URL you control; it belongs to one domain, which is why listing them REQUIRES `domain_id`. ⚠ MAILERSEND CALLS `url` BEFORE IT SAVES THE WEBHOOK and refuses one that does not answer a POST. Measured 2026-09-19: creating a webhook pointed at https://example.com/... answered 422 with MailerSend's own field error `url: The endpoint returned HTTP 405.` -- example.com exists and serves GET, so this is a live reachability check rather than a format check. Supply an endpoint reachable from the public internet that answers POST, or the webhook is never created.

webhooks_full
mailersend_put_domains_by_domain_id_settingsWRITE

Update domain settings. A sending domain is what authorises MailerSend to send `from` an address; a domain that is not verified cannot send.

domains_full
mailersend_put_domains_by_domain_id_smtp_users_by_smtp_user_idWRITE

Update SMTP user. An SMTP user is a per-domain credential for sending over SMTP rather than the API.

smtp_users_full
mailersend_put_identities_by_identity_idWRITE

Update a sender identity. A sender identity authorises ONE address on a domain to send, which is how an account sends `from` an address it has not verified the whole domain for.

sender_identity_full
mailersend_put_identities_email_emailWRITE

Update a sender identity by Email. A sender identity authorises ONE address on a domain to send, which is how an account sends `from` an address it has not verified the whole domain for.

sender_identity_full
mailersend_put_inbound_by_inbound_idWRITE

Update an inbound route. An inbound route receives mail sent TO a subdomain you control and forwards it to a webhook or an address.

inbounds_full
mailersend_put_sms_inbounds_by_sms_inbound_idWRITE

Update an inbound route. An SMS inbound route forwards received texts to a URL.

sms_full
mailersend_put_sms_numbers_by_sms_number_idWRITE

Update a single SMS phone number. Phone numbers are purchased in the MailerSend dashboard, not through the API.

sms_full
mailersend_put_sms_recipients_by_sms_recipient_idWRITE

Update a single SMS recipient. An SMS recipient is a number MailerSend has seen, with its opt-in state.

sms_full
mailersend_put_sms_webhooks_by_sms_webhook_idWRITE

Update a single SMS webhook. An SMS webhook delivers SMS events to a URL you control.

sms_full
mailersend_put_token_by_token_id_settingsWRITE

Update a Token. These manage MailerSend API TOKENS -- the same kind of credential this connection itself holds. The connection's own token must carry API tokens = Full access, and a created token's secret is returned ONCE, in the create response.

tokens_full
mailersend_put_users_by_user_idWRITE

Update User. Users are the people with access to the MailerSend account, and their roles.

users_full
mailersend_put_webhooks_by_webhook_idWRITE

Update a webhook. A webhook delivers email events to a URL you control; it belongs to one domain, which is why listing them REQUIRES `domain_id`.

webhooks_full

Put MailerSend behind one governed endpoint.

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