Not sure it'll hold up? We'll verify 10,000 records free and show you what's in your file.
Check my list →You don't have to be a customer. Most setups we diagnose run on Instantly, Klaviyo or Google Workspace.
Book a diagnosis →A REST API covering every part of the platform that has a screen, 100+ calls across six areas, webhooks that push events to you as they happen, and a Zapier bridge to everything else.
Every part of the platform that has a screen also has an endpoint. Lists, messages, campaigns, sending profiles, reporting, verification and users are all reachable over HTTP, with 100+ calls across six areas. Webhooks push opens, clicks and unsubscribes to you as they happen, and Zapier covers the 2,000+ apps nobody wants to write an integration for.
Generate a key from the API tab inside the platform. You can create as many as you need, which is how you keep a client integration separate from an internal script.
https://api.mailclickconvert.com/api.php ?apikey=YOUR_API_KEY &area=email &action=getlists
<response>
<list>
<id>45911</id>
<title>Q3 Manufacturing</title>
<records>412900</records>
</list>
</response>From the API tab in the platform. Multiple keys per account, so integrations can be revoked one at a time.
Which part of the system you are calling: email, home, clients, listverify, support or api.
The call itself, for example getlists or uploadlistfile.
XML by default. Add output=json or output=csv if you would rather not parse XML.
The full reference with arguments and sample responses lives in the developer docs. This is the shape of it.
emailEmail marketingThe bulk of the API. Lists, messages, campaigns, sending profiles, suppression and reporting.
homeUsersManaging the people on your account.
clientsClientsFor agencies and resellers running many accounts.
listverifyVerificationRunning and monitoring list cleaning jobs.
apiWebhooksManaging your own webhook subscriptions.
supportSupportReading tickets programmatically.
Paging and limits. Calls that return lists accept start and limit, with a ceiling of 1,000 records per request, and return a <records> count so you know how far through you are. Most calls run at the default rate; verifysingleemail is capped at one request per second and returns a plain rate-limit error rather than failing silently.
Point a webhook at a URL and the platform posts JSON as things happen. Opens, clicks and unsubscribes are the events most people wire up, and unsubscribes are the one you should not skip: acting on them in your own database is what keeps your suppression honest.
timestamp is a UNIX timestamp in CST, not UTC. This catches people out.listmetadata optionally carries every column from your list for that record, so you can match it back without a second lookup.POST https://yourapp.com/hooks/mcc
Content-Type: application/json
[{ "event": "unsubscribe",
"email": "someone@example.com",
"listid": 45911,
"timestamp": 1770000000,
"listmetadata": { "company": "Acme", "state": "TX" } }]2,000+ apps over webhooks. Add to a list, unsubscribe, or push a reply into your CRM without touching the API.
Send through the platform over plain SMTP, or connect providers you already pay for. See SMTP relay.
Retrieve mail programmatically rather than through the reply inbox.
SendGrid, Amazon SES, Mailgun, Postmark or SMTP.com connected and rotated from one account.
Pixels and links to attribute conversions and revenue back to a campaign.
Reputation and spam-rate data pulled in alongside your own reporting.
Major ISP feedback loops supported, with complaints auto-unsubscribing.
The API can be extended for a specific use case. Ask, and we will tell you honestly whether it is worth building.
output=json or output=csv to the request if you would rather not parse XML. The same call returns the same data in whichever format you ask for.verifysingleemail is capped at one request per second and returns a clear rate-limit error rather than failing silently. Calls that return lists cap at 1,000 records per request, so large pulls are paged with start and limit.Describe the outcome rather than the endpoint. There is often an existing call that already does it, and if there is not we will say whether it is worth building.
Full endpoint documentation with arguments and sample responses is in the developer docs. If you would rather describe the problem than read 100 endpoints, the call is free.