Canadian software teams, from Waterloo start-ups to Montreal e-commerce shops, need their applications to send email reliably: order confirmations, password resets, invoices, shipping notices. Mailpro’s email API lets your code send those messages directly, with delivery tracking and webhooks, while the data stays on Swiss-hosted infrastructure.
What you can send through the API
- Order confirmations and receipts, with GST/HST or QST amounts from your own system.
- Account emails: sign-up verification, password resets, security alerts.
- Booking confirmations for clinics, restaurants and tour operators.
- Invoices and payment reminders for subscription services.
- Notifications from internal tools and dashboards.
Transactional messages and CASL
CASL distinguishes between commercial messages and those that facilitate a transaction the recipient already agreed to. A receipt, a warranty notice or factual information about an account a person holds is generally exempt from the consent requirement, though it still needs sender identification and, where required, an unsubscribe mechanism. Once you add promotional content, such as a discount on the next order, the message becomes commercial and needs consent. Keep API templates strictly transactional, and send marketing through your campaign lists. The transactional email definition explains the difference.
How the integration works
Authenticate with your API key, call the send endpoint with the recipient, subject and content (or a stored template), and receive a message ID. The API documentation covers endpoints and code samples. Store the contact’s language so your application can pick the English or French template automatically.
Know what happened to every message
Each message can be tracked through delivery, opens, clicks and bounces. Rather than polling, subscribe to webhooks so your application is notified in real time. Our FAQ on Mailpro’s webhook types explains which events you can receive, and the page on email API statistics shows how to read the results.
Privacy and data residency
Transactional emails carry personal information: names, addresses, order contents. Under PIPEDA you remain accountable for that data when a service provider processes it, and Quebec’s Law 25 requires a privacy impact assessment before it leaves the province. Mailpro processes and stores messages in Switzerland on private infrastructure, outside US jurisdiction, with TLS 1.3 encryption, and never sells or rents data. See whether your email data is subject to US law for background.
English and French templates
A bilingual application usually stores a language preference per user. Create each transactional template in both languages, give them matching identifiers, and let your code select the right one. Keep dates, amounts and addresses in Canadian formats for each language: “October 12, 2026” and “$49.99” in English, “12 octobre 2026” and “49,99 $” in French. Small details like these reduce support tickets.
Built for real-world volume
Transactional volume in Canada follows the retail calendar: a quiet summer, then Thanksgiving, Black Friday and Boxing Day peaks. The API accepts messages as they are generated, and delivery reporting lets you confirm that confirmations went out during the busiest hours. In Mailpro’s own customer survey, email deliverability is rated 9.6/10.
API or SMTP?
If your platform already sends through SMTP, such as a WordPress site or an older ERP, a relay may be quicker to set up. If you’re writing new code, the API gives you more control. Our comparison of API versus SMTP for Canadian teams helps you choose, and the API product page lists the features.