When your booking engine or client portal sends emails through Mailpro’s API, every message leaves a trail. API statistics let you follow that trail, both in Mailpro’s dashboard and inside your own software. For businesses in St Kitts and Nevis, where most recipients are overseas and a missed email can mean a missed flight or payment, that visibility is valuable.

Three ways to get the data

1. In the dashboard

Mailpro’s reporting shows totals and trends: messages sent, delivered, bounced, opened and clicked, over any period. Global statistics combine API, SMTP and campaign sends so you can see all your email in one place.

2. By asking the API

Each send returns a message ID. Your system can call the status endpoint with that ID to learn whether the message is queued, sent, delivered, deferred or bounced. That is how a hotel’s reservation screen can show a green tick next to Confirmation delivered.

3. Through webhooks

Instead of asking, your system can be told. Webhooks notify your application the moment something happens: a delivery, a bounce, a click. A tour operator can use a bounce event to trigger an SMS to the guest’s +1 869 or overseas number instead.

Which figures matter most

  • Bounces, split into hard (address doesn’t exist) and soft (temporary problem). Hard bounces usually point to typos at booking; fix the form.
  • Deferrals, which can indicate that a receiving provider is throttling your domain; check your authentication.
  • Clicks on key links, such as the payment link in an invoice or the check-in link in a pre-arrival email.
  • Location, from geo-tracking, which shows where emails are opened and can help schedule by time zone.

Timing and time zones

The Federation runs on Atlantic Standard Time all year. API sends go out immediately unless you delay them in your code or use scheduled sending. If your statistics show that pre-arrival emails sent at 3 a.m. European time are opened far less, move the trigger.

Putting the data to work

Statistics are most valuable when they change what your system does. Some practical uses: flag bookings whose confirmation bounced so front-desk staff can phone the guest; suppress addresses that have hard-bounced so your domain reputation stays healthy; and compare click rates on payment links in invoices sent at different times of day. For firms handling Citizenship by Investment files, a delivery record for each client notice can support your audit trail.

Keeping statistics lawful

Event data such as opens, clicks and locations are linked to individuals, so they count as personal data. The Federation’s Data Protection Act, 2018 asks businesses to keep data only as long as needed and to protect it. Store only the events you use, set a retention period, and remember that Mailpro keeps its copy in Switzerland, outside US jurisdiction.

New to the API? Start with the email API overview for St Kitts and Nevis. Plans and sending volumes are on the pricing page linked below.

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}/Status tells 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.

Connect your app to Mailpro from Saint Kitts and Nevis

Send transactional and marketing email through a REST API, with delivery statuses and webhooks. Start free with 500 credits.