If your Ghanaian business sends email from software, whether an online shop, a school portal, a banking app or an ERP, you have two ways to connect to Mailpro: the SMTP relay or the HTTP API. Both deliver email; they differ in how your software talks to the service. Here is how to choose.
The short version
| SMTP relay | Email API | |
|---|---|---|
| Set-up | Enter host, port and credentials in existing software | Write code against the API |
| Best for | WordPress, accounting tools, ERPs, legacy systems | Custom apps, fintech platforms, SaaS products |
| Error handling | Basic SMTP response codes | Structured JSON responses |
| Extra features | Sending only | Sending plus contacts, lists and statistics |
| Speed to launch | Very quick | Needs developer time |
When SMTP is the right choice
SMTP is universal. Almost every piece of software that sends email already supports it, so you can switch a WooCommerce shop, a hospital booking system or a Sage installation to Mailpro in minutes without writing code. This suits many Ghanaian SMEs that rely on off-the-shelf tools and do not have in-house developers. Read what is SMTP for background and Mailpro’s SMTP server for Ghana for set-up.
When the API is the better fit
If you are building your own product, the API gives you more. Fintech and e-commerce teams in Accra often need to know instantly whether an OTP or receipt was accepted, to sync contact data between their app and marketing lists, and to receive events via webhooks. The Mailpro API for Ghana supports all three.
Considerations specific to Ghana
Connectivity
Both methods run server to server, so your customers’ mobile connections do not affect sending. What matters is that your server can reach Mailpro reliably; build retries into your code in case of brief outages on your side.
Combining email with SMS
Many Ghanaian services send a text alongside an email, for example a MoMo payment confirmation followed by an emailed receipt. Mailpro handles both, so an API integration can cover both channels.
Compliance
Whichever method you use, transactional and marketing streams should be kept apart. Marketing content requires prior consent under section 40 of the Data Protection Act, 2012 (Act 843), and every marketing message needs an unsubscribe option under the Electronic Transactions Act, 2008 (Act 772).
Security
Both routes are encrypted with TLS 1.3, and data is held on private Swiss infrastructure, outside US jurisdiction. Configure SPF, DKIM and DMARC whichever route you choose; our article on SMTP relay vs email API goes deeper into the technical trade-offs.
A worked example: a fintech in Accra
Imagine a savings app that lets customers top up with mobile money. It sends four kinds of email: a verification link at sign-up, a receipt after each top-up, a monthly statement, and an occasional product newsletter to customers who opted in.
- Verification and receipts go through the API. The app needs an immediate answer if a send fails, so it can show an error on screen or fall back to SMS.
- Monthly statements are generated by the core banking system, which already supports SMTP. Pointing it at Mailpro’s relay takes minutes and needs no code changes.
- The newsletter is built by the marketing team in the Mailpro editor and sent to the consented segment, with an unsubscribe link in every issue.
Three streams, two technical routes, one account and one set of statistics.
Switching later
The choice is not permanent. Many Ghanaian teams start with SMTP because it works immediately, then move high-volume or critical flows to the API once they have developer capacity. Because both routes use the same Mailpro account, domain authentication and statistics carry over.
Questions to ask before you decide
- Does the software that sends the email already support SMTP settings?
- Do you have developer time to write and maintain an integration?
- Do you need to sync contacts or read statistics from your own systems?
- How quickly must your app react to a failed send?
If you answered yes to the first question and no to the others, start with SMTP. Otherwise, the API is likely worth the extra effort.
Using both
Many organisations do. A bank might send statements from its core system via SMTP and app notifications via the API. Mailpro reports on both in one account; see API statistics and SMTP statistics.