An email API lets your website, app or back-office system send email by making an HTTP request, instead of a person clicking “send”. Australian online stores use it for order and shipping confirmations, booking platforms for reminders, SaaS products for password resets, and councils and clubs for membership notices. Mailpro’s REST API handles the sending, tracking and bounce management so your developers don’t have to run their own mail servers.
What you can do with the Mailpro API
- Send single transactional emails, such as receipts, invoices and account alerts.
- Trigger marketing campaigns or add contacts to lists from your own CRM.
- Track delivery status, opens and clicks, and receive events through webhooks.
- Manage contacts, including unsubscribes, so opt-outs from your app reach your email lists.
- Send SMS to +61 mobiles through the same platform.
Full details are on the email API page and in our FAQ on delivery status for transactional emails.
Transactional or commercial? It matters under the Spam Act
The Spam Act 2003 applies to commercial electronic messages. A plain order confirmation or password reset is generally not commercial, so it doesn’t need marketing consent. But the ACMA looks at content, not labels: if a transactional email also promotes products or the brand, it becomes a commercial message and needs consent, sender identification and an unsubscribe. The Commonwealth Bank’s $7.5 million penalty in 2024 involved millions of messages the bank had classed as non-commercial (ACMA). Keep promotions out of your API-sent transactional templates, or treat those templates as marketing.
Data residency and APP 8
An email API sees a lot of personal information: names, addresses, order details, sometimes health or financial context. If your business is covered by the Privacy Act 1988, APP 8 requires reasonable steps before disclosing that information to an overseas provider. Mailpro processes and stores all data in Switzerland on its own private infrastructure, outside US jurisdiction, with TLS 1.3 encryption in transit. Switzerland also holds an EU adequacy decision, which helps if you have European customers. Read more on why hosting location matters.
API or SMTP?
If your platform can only send through SMTP, such as an older e-commerce plugin or an accounting package, use Mailpro’s SMTP server instead. If you are building new integrations, the API gives richer data and finer control. Our comparison of API versus SMTP helps you choose.
Built for Australian traffic patterns
Transactional volume in Australia peaks around EOFY in June, Click Frenzy and Black Friday in spring, and the Christmas and Boxing Day period. Plan capacity for those spikes, and remember that your own send logic should respect local time for any non-urgent messages. Pricing is based on the emails you send, not on the number of contacts stored.
Getting started with the API
- Create a Mailpro account and generate API credentials.
- Authenticate your sending domain with SPF, DKIM and DMARC, so Australian and international mail providers trust your messages.
- Build your transactional templates, keeping promotional content out of them.
- Send test messages to Gmail, Outlook and Apple Mail addresses, and to a large Australian ISP mailbox if many of your customers use one.
- Set up webhooks for bounces and delivery events, so your application can react.
- Go live, then watch the statistics for the first few days.
Monitoring
Every API send is logged. You can see which messages were delivered, which bounced and why, and which were opened. See our guide to email API statistics for the metrics to watch. In Mailpro’s own customer survey, users rated email deliverability 9.6/10.