Sending through an API is only half the job. The other half is knowing whether the booking confirmation reached a guest in Houston, whether the invoice reminder was opened in Orange Walk, and which link in last week’s promotion drew clicks. Mailpro’s API returns this data to your own software so you can act on it, instead of logging in to a separate dashboard.
The data you can retrieve
Delivery status per message
Every transactional email sent through the API gets an identifier. You can query its status (queued, sent, delivered, deferred or bounced) and record it against the booking, order or client file. This helps when a customer says “I never got it”: you can check the status and resend or switch to SMS.
Opens and clicks, with dates and times
For campaigns, the API returns who opened and who clicked, when and on which link. Because Belize stays on Central Standard Time all year while the US and Canada change their clocks, looking at open times by hour is the reliable way to find when each audience actually reads. Combine it with scheduled sending to time the next campaign.
Country breakdown
Open and click statistics can be downloaded by country for a given campaign. For Belize senders this is especially useful, because many lists mix local residents with North American and European past guests or clients. If a resort’s summer offer is clicked mostly from Canada and a supermarket’s weekly deals only from Belize, you know how to split future campaigns. Geo-tracking shows the same data visually in the dashboard.
Bounces and unsubscribes
Hard bounces and unsubscribes come back through the API so your CRM stops treating them as reachable contacts. Under Belize’s Data Protection Act, 2021, people can require you to stop direct marketing to them, so syncing unsubscribes back to every system that holds the address is good practice.
Turning numbers into decisions
| What you see | What to check |
|---|---|
| Transactional emails delayed or deferred | Authentication of your sending domain (SPF, DKIM, DMARC) |
| Low opens from one country | Send time for that time zone and the subject-line language |
| High clicks but few bookings | The landing page on mobile, since most local readers use phones |
| Rising bounces on an old list | Remove stale addresses and re-confirm consent |
Real-time notifications instead of polling
If you prefer to be told rather than to ask, webhooks push events such as delivered, bounced or new contact to your endpoint as they happen. A booking system can then flag a failed confirmation straight away. See the three types of Mailpro webhooks.
Where the numbers are kept
Tracking data is personal data: it records what a named person did and when. Mailpro keeps it on its own servers in Switzerland, outside US jurisdiction, and never sells or rents it. This fits the Belize Act’s expectation of adequate protection when data leaves the country. For campaign-level reporting without code, use Mailpro’s statistics and reports. To get started with sending, see our email API overview for Belize.
Documentation and resources for developers
All the technical documentation of the Mailpro APIs lives on the developer portal: Email API v2, CRM API v3 and SMS API, described endpoint by endpoint (OpenAPI), in English and five other languages.
- Delivery tracking of transactional emails — every single send returns an identifier;
GET /Send/{id}/Statustells you whether it is queued, sent, delivered, deferred or bounced. In detail. - Webhooks — three directions: Mailpro notifies you (email delivered, bounce, new contact…), your automations call your tools, an external tool triggers an automation. The three types of webhooks · reference.
- Frequently asked questions — authentication, limits, attachments, Zapier / Make / n8n: API & Webhooks FAQ.
Overview of the three APIs and code samples: the Mailpro API page.