Email API vs SMTP: A Guide for New Zealand Teams

A Christchurch retailer connecting an online store, a Wellington start-up building a booking app and a Tauranga trade supplier running an older ERP system all need to send email from software. Each will end up choosing between two routes: SMTP, the standard protocol that almost every application can speak, or an email API, where your code calls a web service directly. Neither is better in the abstract. The right answer depends on what you are connecting and how much control you want.

The two methods in plain terms

SMTP (Simple Mail Transfer Protocol) is how email servers have passed messages to each other for decades. You give your application a server name, a port, a username and a password, and it hands each message to that server for delivery. Mailpro provides an SMTP server for exactly this.

An email API is a set of web endpoints. Your code sends a request containing the recipient, the content or template, and any personalisation data, and receives a structured response, including an identifier you can use to check delivery status. Mailpro’s email API also covers contacts and statistics.

Side-by-side comparison

Three New Zealand scenarios

The online shop. Most e-commerce and website platforms already have an SMTP field. Pointing it at Mailpro takes a few minutes and immediately improves on sending from a shared web host. Check the right port for your platform; our article on port 465 vs port 587 explains the difference.

The booking platform. A developer building for tour operators wants to know whether each confirmation arrived and to pull engagement by country for international guests. The API fits better, with API statistics feeding the operator’s dashboard.

The mixed setup. Plenty of businesses use both: SMTP for the accounting system’s invoices and the API for the customer app. A single Mailpro account can serve both. For a deeper technical comparison, read SMTP relay vs email API.

The law does not care which pipe you use

New Zealand’s Unsolicited Electronic Messages Act 2007 applies to commercial electronic messages whether they leave through SMTP or an API. Marketing messages need consent, accurate sender details and a functional unsubscribe facility, and opt-outs must be honoured within 5 working days. Pure transactional messages, such as an order confirmation for a purchase the customer agreed to, are treated differently, but only as long as they stay factual. Our page on New Zealand email marketing law covers the details, and automated emails shows how to build compliant journeys without code.

Whichever you choose, authenticate your domain with SPF, DKIM and DMARC; the authentication guide walks through the records.

Where the data goes

There is no requirement in the Privacy Act 2020 to send email through servers located in New Zealand. What matters is that personal information is protected and that you stay accountable for it when a provider holds it on your behalf. Mailpro’s SMTP and API traffic both run on Swiss-hosted private infrastructure, outside US jurisdiction, with TLS 1.3 encryption in transit.