DEVELOPERS API documentation

The MailClickConvert API.

A REST API over everything in the platform that has a screen. Generate keys from the API tab inside the software — as many as you need, each with its own access — and call 108 documented endpoints across six areas, GET or POST, with XML, JSON or CSV back.

At a glance
  • One endpoint, GET or POST
  • XML, JSON or CSV
  • 1,000 records a page
  • Webhooks with retries
  • MCP server for AI agents
Basics

Three parameters on every request.

Every call goes to the same endpoint. apikey, area and action are always required; anything else depends on the call. GET and POST both work unless a call's page says otherwise.

Request
https://api.mailclickconvert.com/api.php
  ?apikey=YOUR_API_KEY
  &area=home
  &action=getusers
Response
<response>
  <user>
    <id>1337</id>
    <firstname>John</firstname>
    <lastname>Doe</lastname>
    <username>username</username>
    <email>test@test.com</email>
    <lastlogin>October 17, 2025, 03:15:17 pm</lastlogin>
    <primaryuser>No</primaryuser>
  </user>
</response>
01

apikey

Generated under the API tab in the platform. Create one per integration and decide what each key can reach, so a client script can be revoked without touching anything else.

02

area

The part of the system you're calling: email, home, clients, listverify, api or support.

03

action

The call itself — getcampaigns, addemail, uploadlistfile. All 108 are listed by area.

04

output

XML by default. Add output=json or output=csv to get either instead. Errors use the same envelope in every format.

Paging

start, limit, and a records count.

Calls that return lists take start (position in the result set) and limit (records per page, up to 1,000). Every page also carries a <records> element with the total, so you know when you've reached the end.

Request
https://api.mailclickconvert.com/api.php
  ?apikey=YOUR_API_KEY
  &area=email
  &action=getmessages
  &start=0&limit=5
Response
<response>
  <records>2</records>
  <message>
    <id>45911</id>
    <title>Message 1</title>
    <datecreated>August 11, 2025, 09:18:08 pm</datecreated>
    <numberoftimesused>0</numberoftimesused>
    <datelastused>Never</datelastused>
    <locked>0</locked>
  </message>
  <message>
    <id>45910</id>
    <title>Message 2</title>
    <datecreated>August 11, 2025, 09:17:39 pm</datecreated>
    <numberoftimesused>2</numberoftimesused>
    <datelastused>October 11, 2020, 11:42:04 pm</datelastused>
    <locked>0</locked>
  </message>
</response>
Errors and limits

Ten calls a second, one for verification.

The default limit is 10 calls a second per key. verifysingleemail is limited to one call a second. Go over either and the call returns an error instead of queueing — so if you're looping, sleep for a second or two between calls.

Any error
<response>
  <error>Error Message Appears Here</error>
</response>
Rate limit exceeded
<response>
  <error>Rated Limited 1 API Query a Second</error>
</response>
Samples

The same call in three languages.

getcampaigns with JSON output and the first page of ten. Swap the area and action for any call in the list.

curl "https://api.mailclickconvert.com/api.php?apikey=YOUR_API_KEY&area=email&action=getcampaigns&output=json&start=0&limit=10"
AI agents

There's an MCP server, too.

The platform ships a Model Context Protocol server that wraps this API, so an AI agent — Claude, Cursor, or anything else that speaks MCP — can list campaigns, add contacts or pull results in plain language instead of query strings. Every action is classified read, write or destructive, so you can decide how much you let an agent do. You'll find it inside the platform.

Need a call that isn't here?

Custom integration work is quoted on scope, and support is a person on weekdays, 9am to 5pm CST.