Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
All 92 tools →
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/mailchimp-senders-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no email required.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
version: 1.4.1
title: Mailchimp Transactional Senders API
contact:
name: API Support
email: apihelp@mailchimp.com
x-permalink: https://github.com/mailchimp/mailchimp-client-lib-codegen/blob/main/spec/transactional.openapi.json
servers:
- url: https://mandrillapp.com/api/1.3
tags:
- name: senders
paths:
/senders/list:
post:
x-custom-config:
methodNameCamel: list
methodNameSnake: list
summary: List account senders
description: Return the senders that have tried to use this account.
operationId: postSendersList
tags:
- senders
responses:
'200':
description: ''
content:
application/json:
schema:
type: array
description: an array of sender data, one for each sending addresses used by the account
items:
type: object
description: the information on each sending address in the account
properties:
address:
type: string
format: email
description: the sender's email address
example: user@example.com
created_at:
type: string
format: date-time
description: the date and time that the sender was first seen by Mandrill as a UTC date string in YYYY-MM-DD HH:MM:SS format
example: '2025-04-15 13:00:00.18061'
sent:
type: integer
description: the total number of messages sent by this sender
example: 20
hard_bounces:
type: integer
description: the total number of hard bounces by messages by this sender
example: 5
soft_bounces:
type: integer
description: the total number of soft bounces by messages by this sender
example: 2
rejects:
type: integer
description: the total number of rejected messages by this sender
example: 1
complaints:
type: integer
description: the total number of spam complaints received for messages by this sender
example: 0
unsubs:
type: integer
description: the total number of unsubscribe requests received for messages by this sender
example: 0
opens:
type: integer
description: the total number of times messages by this sender have been opened
example: 10
clicks:
type: integer
description: the total number of times tracked URLs in messages by this sender have been clicked
example: 5
unique_opens:
type: integer
description: the number of unique opens for emails sent for this sender
example: 8
unique_clicks:
type: integer
description: the number of unique clicks for emails sent for this sender
example: 3
application/x-php:
schema:
type: array
description: an array of sender data, one for each sending addresses used by the account
items:
type: object
description: the information on each sending address in the account
properties:
address:
type: string
format: email
description: the sender's email address
example: user@example.com
created_at:
type: string
format: date-time
description: the date and time that the sender was first seen by Mandrill as a UTC date string in YYYY-MM-DD HH:MM:SS format
example: '2025-04-15 13:00:00.18061'
sent:
type: integer
description: the total number of messages sent by this sender
example: 20
hard_bounces:
type: integer
description: the total number of hard bounces by messages by this sender
example: 5
soft_bounces:
type: integer
description: the total number of soft bounces by messages by this sender
example: 2
rejects:
type: integer
description: the total number of rejected messages by this sender
example: 1
complaints:
type: integer
description: the total number of spam complaints received for messages by this sender
example: 0
unsubs:
type: integer
description: the total number of unsubscribe requests received for messages by this sender
example: 0
opens:
type: integer
description: the total number of times messages by this sender have been opened
example: 10
clicks:
type: integer
description: the total number of times tracked URLs in messages by this sender have been clicked
example: 5
unique_opens:
type: integer
description: the number of unique opens for emails sent for this sender
example: 8
unique_clicks:
type: integer
description: the number of unique clicks for emails sent for this sender
example: 3
application/x-yaml; charset=utf-8:
schema:
type: array
description: an array of sender data, one for each sending addresses used by the account
items:
type: object
description: the information on each sending address in the account
properties:
address:
type: string
format: email
description: the sender's email address
example: user@example.com
created_at:
type: string
format: date-time
description: the date and time that the sender was first seen by Mandrill as a UTC date string in YYYY-MM-DD HH:MM:SS format
example: '2025-04-15 13:00:00.18061'
sent:
type: integer
description: the total number of messages sent by this sender
example: 20
hard_bounces:
type: integer
description: the total number of hard bounces by messages by this sender
example: 5
soft_bounces:
type: integer
description: the total number of soft bounces by messages by this sender
example: 2
rejects:
type: integer
description: the total number of rejected messages by this sender
example: 1
complaints:
type: integer
description: the total number of spam complaints received for messages by this sender
example: 0
unsubs:
type: integer
description: the total number of unsubscribe requests received for messages by this sender
example: 0
opens:
type: integer
description: the total number of times messages by this sender have been opened
example: 10
clicks:
type: integer
description: the total number of times tracked URLs in messages by this sender have been clicked
example: 5
unique_opens:
type: integer
description: the number of unique opens for emails sent for this sender
example: 8
unique_clicks:
type: integer
description: the number of unique clicks for emails sent for this sender
example: 3
deprecated: false
requestBody:
content:
application/json:
schema:
type: object
required:
- key
properties:
key:
type: string
description: a valid api key
required: true
/senders/domains:
post:
x-custom-config:
methodNameCamel: domains
methodNameSnake: domains
summary: List sender domains
description: Returns the sender domains that have been added to this account.
operationId: postSendersDomains
tags:
- senders
responses:
'200':
description: ''
content:
application/json:
schema:
type: array
description: an array of sender domain data, one for each sending domain used by the account
items:
type: object
description: the information on each sending domain for the account
properties:
domain:
type: string
description: the sender domain name
example: example.com
created_at:
type: string
format: date-time
description: the date and time that the sending domain was first seen as a UTC string in YYYY-MM-DD HH:MM:SS format
example: '2025-04-15 13:22:49'
last_tested_at:
type: string
format: date-time
description: when the domain's DNS settings were last tested as a UTC string in YYYY-MM-DD HH:MM:SS format
example: '2025-04-29 13:00:00'
spf:
type: object
description: details about the domain's SPF record
properties:
valid:
type: boolean
description: whether the domain's SPF record is valid for use with Mandrill
example: true
valid_after:
type: string
format: date-time
description: when the domain's SPF record will be considered valid for use with Mandrill as a UTC string in YYYY-MM-DD HH:MM:SS format. If set, this indicates that the record is valid now, but was previously invalid, and Mandrill will wait until the record's TTL elapses to start using it.
example: '2025-04-24 14:00:00'
error:
type: string
description: an error describing the spf record, or null if the record is correct
example: This domain has an SPF record, but it doesn't include Mandrill.
dkim:
type: object
description: details about the domain's Legacy DKIM record
properties:
valid:
type: boolean
description: whether the domain's Legacy DKIM record is valid for use with Mandrill
example: false
valid_after:
type: string
format: date-time
description: when the domain's Legacy DKIM record will be considered valid for use with Mandrill as a UTC string in YYYY-MM-DD HH:MM:SS format. If set, this indicates that the record is valid now, but was previously invalid, and Mandrill will wait until the record's TTL elapses to start using it.
example: '2025-04-15 13:00:00'
error:
type: string
description: an error describing the Legacy DKIM record, or null if the record is correct
example: does not match the required CNAME target of dkim1.mandrillapp.com. Please verify that the target was entered exactly as requested and try again.
dkim2:
type: object
description: details about the domain's rotatable 2048 bit DKIM record
properties:
valid:
type: boolean
description: whether the domain's DKIM record is valid for use with Mandrill
example: true
valid_after:
type: string
format: date-time
description: when the domain's DKIM record will be considered valid for use with Mandrill as a UTC string in YYYY-MM-DD HH:MM:SS format. If set, this indicates that the record is valid now, but was previously invalid, and Mandrill will wait until the record's TTL elapses to start using it.
example: '2025-04-15 13:00:00'
error:
type: string
description: an error describing the DKIM record, or null if the record is correct
example: does not match the required CNAME target of dkim2.mandrillapp.com. Please verify that the target was entered exactly as requested and try again.
dmarc:
type: object
description: details about the domain's DMARC record
properties:
valid:
type: boolean
description: whether the domain's DMARC record is valid for use with Mandrill
example: false
error:
type: string
description: an error describing the DMARC record, or null if the record is correct
example: The record doesn't begin with a valid version tag.
verified_at:
type: string
format: date-time
description: if the domain has been verified, this indicates when that verification occurred as a UTC string in YYYY-MM-DD HH:MM:SS format
example: '2025-04-20 13:00:00'
valid_signing:
type: boolean
description: whether this domain can be used to authenticate mail, either for itself or as a custom signing domain. If this is false but spf and dkim are both valid, you will need to verify the domain before using it to authenticate mail
example: false
verify_txt_key:
type: string
description: a unique key used to verify a domain by adding a TXT record. Append this key to 'mandrill_verify.' and add it to your domain's TXT records to verify
example: wtwm-d3lEsGLX6yeb24weA
application/x-php:
schema:
type: array
description: an array of sender domain data, one for each sending domain used by the account
items:
type: object
description: the information on each sending domain for the account
properties:
domain:
type: string
description: the sender domain name
example: example.com
created_at:
type: string
format: date-time
description: the date and time that the sending domain was first seen as a UTC string in YYYY-MM-DD HH:MM:SS format
example: '2025-04-15 13:22:49'
last_tested_at:
type: string
format: date-time
description: when the domain's DNS settings were last tested as a UTC string in YYYY-MM-DD HH:MM:SS format
example: '2025-04-29 13:00:00'
spf:
type: object
description: details about the domain's SPF record
properties:
valid:
type: boolean
description: whether the domain's SPF record is valid for use with Mandrill
example: true
valid_after:
type: string
format: date-time
description: when the domain's SPF record will be considered valid for use with Mandrill as a UTC string in YYYY-MM-DD HH:MM:SS format. If set, this indicates that the record is valid now, but was previously invalid, and Mandrill will wait until the record's TTL elapses to start using it.
example: '2025-04-24 14:00:00'
error:
type: string
description: an error describing the spf record, or null if the record is correct
example: This domain has an SPF record, but it doesn't include Mandrill.
dkim:
type: object
description: details about the domain's Legacy DKIM record
properties:
valid:
type: boolean
description: whether the domain's Legacy DKIM record is valid for use with Mandrill
example: false
valid_after:
type: string
format: date-time
description: when the domain's Legacy DKIM record will be considered valid for use with Mandrill as a UTC string in YYYY-MM-DD HH:MM:SS format. If set, this indicates that the record is valid now, but was previously invalid, and Mandrill will wait until the record's TTL elapses to start using it.
example: '2025-04-15 13:00:00'
error:
type: string
description: an error describing the Legacy DKIM record, or null if the record is correct
example: does not match the required CNAME target of dkim1.mandrillapp.com. Please verify that the target was entered exactly as requested and try again.
dkim2:
type: object
description: details about the domain's rotatable 2048 bit DKIM record
properties:
valid:
type: boolean
description: whether the domain's DKIM record is valid for use with Mandrill
example: true
valid_after:
type: string
format: date-time
description: when the domain's DKIM record will be considered valid for use with Mandrill as a UTC string in YYYY-MM-DD HH:MM:SS format. If set, this indicates that the record is valid now, but was previously invalid, and Mandrill will wait until the record's TTL elapses to start using it.
example: '2025-04-15 13:00:00'
error:
type: string
description: an error describing the DKIM record, or null if the record is correct
example: does not match the required CNAME target of dkim2.mandrillapp.com. Please verify that the target was entered exactly as requested and try again.
dmarc:
type: object
description: details about the domain's DMARC record
properties:
valid:
type: boolean
description: whether the domain's DMARC record is valid for use with Mandrill
example: false
error:
type: string
description: an error describing the DMARC record, or null if the record is correct
example: The record doesn't begin with a valid version tag.
verified_at:
type: string
format: date-time
description: if the domain has been verified, this indicates when that verification occurred as a UTC string in YYYY-MM-DD HH:MM:SS format
example: '2025-04-20 13:00:00'
valid_signing:
type: boolean
description: whether this domain can be used to authenticate mail, either for itself or as a custom signing domain. If this is false but spf and dkim are both valid, you will need to verify the domain before using it to authenticate mail
example: false
verify_txt_key:
type: string
description: a unique key used to verify a domain by adding a TXT record. Append this key to 'mandrill_verify.' and add it to your domain's TXT records to verify
example: wtwm-d3lEsGLX6yeb24weA
application/x-yaml; charset=utf-8:
schema:
type: array
description: an array of sender domain data, one for each sending domain used by the account
items:
type: object
description: the information on each sending domain for the account
properties:
domain:
type: string
description: the sender domain name
example: example.com
created_at:
type: string
format: date-time
description: the date and time that the sending domain was first seen as a UTC string in YYYY-MM-DD HH:MM:SS format
example: '2025-04-15 13:22:49'
last_tested_at:
type: string
format: date-time
description: when the domain's DNS settings were last tested as a UTC string in YYYY-MM-DD HH:MM:SS format
example: '2025-04-29 13:00:00'
spf:
type: object
description: details about the domain's SPF record
properties:
valid:
type: boolean
description: whether the domain's SPF record is valid for use with Mandrill
example: true
valid_after:
type: string
format: date-time
description: when the domain's SPF record will be considered valid for use with Mandrill as a UTC string in YYYY-MM-DD HH:MM:SS format. If set, this indicates that the record is valid now, but was previously invalid, and Mandrill will wait until the record's TTL elapses to start using it.
example: '2025-04-24 14:00:00'
error:
type: string
description: an error describing the spf record, or null if the record is correct
example: This domain has an SPF record, but it doesn't include Mandrill.
dkim:
type: object
description: details about the domain's Legacy DKIM record
properties:
valid:
type: boolean
description: whether the domain's Legacy DKIM record is valid for use with Mandrill
example: false
valid_after:
type: string
format: date-time
description: when the domain's Legacy DKIM record will be considered valid for use with Mandrill as a UTC string in YYYY-MM-DD HH:MM:SS format. If set, this indicates that the record is valid now, but was previously invalid, and Mandrill will wait until the record's TTL elapses to start using it.
example: '2025-04-15 13:00:00'
error:
type: string
description: an error describing the Legacy DKIM record, or null if the record is correct
example: does not match the required CNAME target of dkim1.mandrillapp.com. Please verify that the target was entered exactly as requested and try again.
dkim2:
type: object
description: details about the domain's rotatable 2048 bit DKIM record
properties:
valid:
type: boolean
description: whether the domain's DKIM record is valid for use with Mandrill
example: true
valid_after:
type: string
format: date-time
description: when the domain's DKIM record will be considered valid for use with Mandrill as a UTC string in YYYY-MM-DD HH:MM:SS format. If set, this indicates that the record is valid now, but was previously invalid, and Mandrill will wait until the record's TTL elapses to start using it.
example: '2025-04-15 13:00:00'
error:
type: string
description: an error describing the DKIM record, or null if the record is correct
example: does not match the required CNAME target of dkim2.mandrillapp.com. Please verify that the target was entered exactly as requested and try again.
dmarc:
type: object
description: details about the domain's DMARC record
properties:
valid:
type: boolean
description: whether the domain's DMARC record is valid for use with Mandrill
example: false
error:
type: string
description: an error describing the DMARC record, or null if the record is correct
example: The record doesn't begin with a valid version tag.
verified_at:
type: string
format: date-time
description: if the domain has been verified, this indicates when that verification occurred as a UTC string in YYYY-MM-DD HH:MM:SS format
example: '2025-04-20 13:00:00'
valid_signing:
type: boolean
description: whether this domain can be used to authenticate mail, either for itself or as a custom signing domain. If this is false but spf and dkim are both valid, you will need to verify the domain before using it to authenticate mail
example: false
verify_txt_key:
type: string
description: a unique key used to verify a domain by adding a TXT record. Append this key to 'mandrill_verify.' and add it to your domain's TXT records to verify
example: wtwm-d3lEsGLX6yeb24weA
deprecated: false
requestBody:
content:
application/json:
schema:
type: object
required:
- key
properties:
key:
type: string
description: a valid api key
required: true
/senders/add-domain:
post:
x-custom-config:
methodNameCamel: addDomain
methodNameSnake: add_domain
summary: Add sender domain
description: Adds a sender domain to your account. Sender domains are added automatically as you send, but you can use this call to add them ahead of time.
operationId: postSendersAddDomain
tags:
- senders
responses:
'200':
description: ''
content:
application/json:
schema:
type: object
description: information about the domain
properties:
domain:
type: string
description: the sender domain name
example: example.com
created_at:
type: string
format: date-time
description: the date and time that the sending domain was first seen as a UTC string in YYYY-MM-DD HH:MM:SS format
example: '2025-04-15 13:22:49'
last_tested_at:
type: string
format: date-time
description: when the domain's DNS settings were last tested as a UTC string in YYYY-MM-DD HH:MM:SS format
example: '2025-04-29 13:00:00'
spf:
type: object
description: details about the domain's SPF record
properties:
valid:
type: boolean
description: whether the domain's SPF record is valid for use with Mandrill
example: true
valid_after:
type: string
format: date-time
description: when the domain's SPF record will be considered valid for use with Mandrill as a UTC string in YYYY-MM-DD HH:MM:SS format. If set, this indicates that the record is valid now, but was previously invalid, and Mandrill will wait until the record's TTL elapses to start using it.
example: '2025-04-24 14:00:00'
error:
type: string
description: an error describing the spf record, or null if the record is correct
example: This domain has an SPF record, but it doesn't include Mandrill.
dkim:
type: object
description: details about the domain's DKIM record
properties:
valid:
type: boolean
description: whether the domain's DKIM record is valid for use with Mandrill
example: true
valid_after:
type: string
format: date-time
description: when the domain's DKIM record will be considered valid for use with Mandrill as
# --- truncated at 32 KB (132 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/mailchimp/refs/heads/main/openapi/mailchimp-senders-api-openapi.yml