Most teams look at campaign results in the Mailpro interface. But if your sales figures live in a BI tool, your board pack is built from a data warehouse, or your agency reports for several clients at once, you want email data to arrive there automatically. Mailpro’s email API lets you download opening and click-through statistics for a campaign, broken down by country, and feed them into whatever reporting you already use.
What the API returns
- Opens: how many recipients opened, when, and from which country.
- Clicks: which links were clicked, how often and from which country.
- Per-campaign data: results for a specific send, so you can compare campaigns over time.
The same measures appear in the interface as global emailing statistics and geo-tracking. The API simply lets you take them elsewhere.
Why country data matters for a UK sender
Many UK lists are less British than they look. A retailer may ship to Ireland, a university may email alumni worldwide, and a B2B firm may have customers across Europe. Country-level data answers practical questions:
- Should Irish subscribers get their own version? Different currency, different delivery times and different public holidays often justify a separate segment.
- Which time zone should drive the send time? If a large share of clicks come from continental Europe, a send tuned to GMT or BST may arrive an hour late there.
- Which rules apply? Contacts in the EU fall under the EU GDPR and local e-privacy laws as well as your UK obligations. Knowing where your audience is helps you apply the right consent standard.
Using the data well
Watch clicks more than opens. Privacy features in some email apps register opens automatically, so opens are only a rough guide. Clicks show real interest.
Join it with sales data. Add a campaign tag to your links, then combine API click data with orders in your shop or CRM to see revenue by campaign and country.
Automate the pull. A scheduled job that fetches statistics each morning means your dashboard is always current, without anyone exporting spreadsheets.
Who uses API statistics
- Agencies managing several UK clients, who want a single client report rather than logging in to each account.
- Ecommerce teams who report revenue per campaign alongside paid search and social.
- Charities that track appeal performance next to donation data in their CRM.
Keeping statistics lawful
Open and click tracking uses pixels and tracked links, which the ICO treats as storage and access technologies under PECR. Mention tracking in your privacy notice and follow current ICO guidance, which was updated in 2026 after the Data (Use and Access) Act 2025. When you download statistics into your own systems, those copies become your responsibility under UK GDPR. Keep access limited and retention sensible. On Mailpro’s side, the data is stored on private Swiss infrastructure, outside US jurisdiction.
Deciding how to integrate? Compare the API and SMTP routes, and see what the interface already shows in campaign statistics.
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.