Email API for St Kitts and Nevis

For many businesses in St Kitts and Nevis, the most important emails are not written by a person at all. They are generated by a booking engine, a property-management system, an e-commerce site or a client portal. An email API lets those systems send through Mailpro directly, with full control over content and timing, and with delivery data coming back to your software.

What the API is for

An API, or application programming interface, is a set of endpoints your developers call over HTTPS. Mailpro’s email API covers three areas:

• Email: send transactional messages one by one or in batches, using your own templates or Mailpro’s.
• Contacts: add, update and segment contacts from your own database, so your mailing lists stay in step with bookings and sign-ups.
• SMS: send text messages to +1 869 numbers and overseas mobiles from the same integration.

Use cases on the islands

• A hotel’s booking engine sends a confirmation instantly, then a pre-arrival email a week before the stay and a text on the morning of arrival.
• A tour operator’s booking app sends e-tickets, and an SMS if a trip is cancelled for weather during hurricane season.
• A firm handling Citizenship by Investment files sends clients secure status updates from its case-management system.
• A school or training provider sends login details and timetable changes from its student system.
• An online shop sends order and shipping notices, with prices in EC$ for local buyers and US$ for overseas orders.

Why developers pick an API over SMTP

An API returns structured responses, a message ID for each send, and delivery events you can store. That makes it easier to build logic such as if the confirmation bounced, show a warning in the booking screen. SMTP is simpler to plug into existing software. The comparison is set out in API versus SMTP.

How an integration usually runs

1. Plan the messages. List every email and text your system should send, when, and to whom. For a hotel, that might be confirmation, pre-arrival, arrival-day SMS, checkout receipt and a post-stay survey.
2. Prepare your domain. Add SPF and DKIM records so mail from your domain is trusted by Gmail, Outlook and Yahoo, where most of your overseas recipients read their email.
3. Build and test. Your developer connects to the API with a key, sends test messages to internal addresses and checks the responses.
4. Handle events. Decide what your system does with bounces and failures, such as flagging the booking or switching to SMS.
5. Go live and monitor. Watch the statistics during the first weeks, particularly before a busy period such as the December to April peak or the St Kitts Music Festival in late June.

Service messages versus marketing

The API can send both, but they are treated differently in law. A confirmation or invoice is part of your contract with the customer. A promotional email needs consent, which is the general approach of the Federation’s Data Protection Act, 2018 and a requirement of laws such as CASL for Canadian recipients. Build that distinction into your code: only send promotional messages to contacts whose consent is recorded.

Security and data location

All API calls are encrypted, and Mailpro hosts data in Switzerland on private infrastructure, outside US jurisdiction. That supports the security principle of the Federation’s Data Protection Act, 2018, which asks businesses to consider where personal data is stored and to use processors that offer sufficient guarantees. For overseas recipients, it also helps with the GDPR; Mailpro’s approach is explained on GDPR compliance.

Track results

Each send can be followed through to delivery, open and click. The figures available and how to use them are covered in email API statistics.

The developer documentation, code samples and webhook references are listed below.