When a guest books a room, a customer pays online or a student resets a password, they expect an email within seconds. Those messages are sent by software, not by a person, and Mailpro’s email API lets Grenadian developers and businesses send them reliably from their own systems.
Who uses an email API in Grenada
- Hotels and villa agencies connecting booking engines to send confirmations, invoices and pre-arrival details.
- Online shops selling spices, chocolate, crafts and fashion to local and overseas customers.
- Service providers such as insurers, utilities or banks sending statements and alerts.
- Education platforms sending account, enrolment and course notifications.
- Local software developers and agencies building apps for clients across the region.
What the Mailpro API does
The Mailpro API lets your application send single or bulk emails, manage contacts and lists, and retrieve statistics. Typical transactional messages include:
- Booking and order confirmations.
- Receipts and invoices, with amounts in EC$ or US$.
- Password resets and account verification.
- Shipping and delivery updates.
- Appointment reminders.
Full technical details are in the developer documentation.
Know what happened to every message
With webhooks, Mailpro notifies your system when an email is delivered, opened, clicked or bounces. If a booking confirmation to a guest in Toronto bounces, your system can flag it so staff can call or text instead. Learn about the three types of Mailpro webhooks and how to check delivery status.
API or SMTP?
If your software can already send through an SMTP server, such as a WordPress site or an accounting package, the Mailpro SMTP server may be quicker to set up. If you are building an integration from scratch, the API offers more control. Our comparison of API and SMTP explains the trade-offs.
Deliverability matters more for transactional email
A lost marketing email is a missed opportunity; a lost booking confirmation is a worried guest. Authenticate your domain with SPF, DKIM and DMARC, keep transactional and marketing traffic separate, and send from a recognisable address. In Mailpro’s own customer survey, users rated email deliverability 9.6/10.
Rules for transactional messages
Service messages that confirm a transaction are generally treated differently from marketing under laws such as CAN-SPAM and CASL. Grenada has no dedicated anti-spam law, and its Data Protection Act, 2023 is not yet in force. Keep transactional emails free of heavy promotion, and only add marketing content for customers who agreed to receive it.
Getting started in four steps
- Create your Mailpro account and generate an API key.
- Authenticate your sending domain with SPF, DKIM and DMARC.
- Build and test your first call, for example sending a booking confirmation to your own address.
- Set up webhooks so your system receives delivery and bounce events.
Start with a single message type, such as order confirmations, check the results for a week, then add others.
Designing transactional templates
Keep transactional emails clear and scannable: a subject that says what the email is (“Your booking at … is confirmed”), key details near the top, and contact information in +1 473 format for local questions. Many recipients will read them on a phone at the airport or on the road, so avoid heavy images.
Handling replies
Set a monitored reply-to address on transactional emails. Guests often reply to a booking confirmation with a question, and those replies should reach a person, not a no-reply inbox.
Secure and Swiss-hosted
API traffic is encrypted with TLS 1.3, and data is hosted in Switzerland on private infrastructure, outside US jurisdiction. Mailpro never sells or rents your data. See how to track results in API email statistics.