
Receipts, account alerts, password resets and booking confirmations should reach the right person with clear information and a useful next step. For Nigerian businesses building these journeys, a good email setup combines sender authentication, a reliable application integration and reporting your team can act on.
Yournotify supports email delivery through an HTTP API and SMTP. This guide explains when to choose each route, how to configure it and how to test a transactional email before connecting it to real customer activity.
Table of Contents
Choose API or SMTP for your application
| Option | A good starting point when… | What your team configures |
|---|---|---|
| Email API | You control the application code and want structured requests and campaign references | Server-side authentication, request payloads and response handling |
| SMTP | Your website, application or plugin already has SMTP settings | Host, port, encryption and gateway credentials |
For a custom booking platform, the API can fit naturally into the booking-confirmed event. For an existing website with an SMTP configuration screen, SMTP may be the quicker integration. Both need a verified sender, useful content and testing.
Avoid connecting the same event to both paths without a deliberate reason. A receipt sent through the API and again through a plugin creates confusion rather than additional reliability.
A familiar Nigerian example: Jumia’s purchase emails
JumiaPay’s Nigerian FAQ explains that a purchase triggers an email notification to the registered Jumia email address after the order and payment are confirmed. This is a useful model for transactional email: the message follows a confirmed business event and helps the buyer understand what happened.
For your own store or service, apply that principle by sending the receipt after your server confirms payment. Include the reference the support team can use, describe the next step and link to the relevant account or order page. A polished email should make the transaction easier to understand, not just announce that your mail integration works.
Email API use cases by industry
| Industry | Transactional email | Information the recipient needs |
|---|---|---|
| Ecommerce | Purchase confirmation | Order reference, purchased items and next steps |
| Education | Registration or fee-payment confirmation | Learner reference, confirmed activity and access details |
| Travel and hospitality | Booking confirmation | Dates, location, booking reference and help contact |
| Professional services | Appointment or invoice notification | Reference, agreed details and the relevant action |
| Membership organisations | Registration or renewal confirmation | Membership status, relevant dates and portal access |
For Nigerian recipients, make naira amounts and payment status unambiguous where they belong in the message. If a payment is still pending, use a pending-payment message rather than a successful-payment receipt. Show appointment times with an appropriate timezone when serving customers in several countries.
Worked example: a hotel booking confirmation
Use a subject such as “Booking confirmed: EX-1042, 18–20 December”. The body can show the guest name, property, arrival and departure dates, booking reference and one button to manage the booking. Keep payment details consistent with the booking record.
When the guest changes dates, send a clearly labelled updated confirmation. Keep the event reference and the booking version in your application so a retry does not send the original dates again.
Test this sequence with a new booking, a modified booking and a failed payment. With Yournotify, the email API or SMTP connection delivers the message; your application supplies the correct event, content and timing.
Step 1: authenticate your sending domain
Open the email sender setup in Yournotify and follow the DNS instructions for the domain you own. Ask the person who manages your DNS to add the records exactly as shown, then confirm verification in the dashboard.
Treat sender authentication as part of the initial setup, not an improvement to add later. Google’s email sender guidelines describe authentication and transport requirements, with additional requirements for bulk senders. Use your account’s generated records rather than copying another business’s DNS values.
Choose a recognisable From name, such as Example Academy, and a sender address on your verified domain. Use a monitored Reply-To address when recipients may need help. A booking confirmation should make it easy to ask a question about that booking.
Step 2: design one clear transactional message
Transactional messages should lead with the event that matters to the recipient. For a training registration, a useful structure is:
- Subject: “Your workshop registration is confirmed”.
- Confirmation: tell the person what succeeded.
- Essential details: workshop, date, time, venue or joining link.
- One primary action: view the booking or add the event to a calendar.
- Help: explain how to contact the organiser.
Keep a readable text version alongside the HTML version. Use actual text for essential details instead of putting everything inside a large image. Test the template with images disabled and on a narrow mobile screen.
Yournotify’s email editor helps teams prepare reusable layouts. For an application-generated message, your developer can also send the required HTML and text in the API request.
Step 3: test the Email API
The following request uses an explicit test email recipient. Replace the sender and recipient with your approved sender ID and an address you control.
curl -X POST 'https://api.yournotify.com/campaigns/email' \
-H "Authorization: Bearer $YOURNOTIFY_API_KEY" \
-H 'Content-Type: application/json' \
-H 'X-YN-SANDBOX: 1' \
--data '{
"name": "Workshop registration confirmation",
"from": "YOUR_APPROVED_EMAIL_SENDER",
"subject": "Your workshop registration is confirmed",
"status": "running",
"lists": ["tester@example.com"],
"html": "<h1>You are registered</h1><p>Your Saturday workshop starts at 10am.</p><p><a href=\"https://example.com/booking\">View your booking</a></p>",
"text": "You are registered. Your Saturday workshop starts at 10am. View your booking: https://example.com/booking"
}'
Set YOURNOTIFY_API_KEY securely in your server environment. The sandbox header validates the payload without delivery or sending charges. Remove it for a controlled live test after validation. An accepted API response is not proof of inbox placement; inspect campaign results and the test mailbox as well.
Use the current API documentation when adding scheduling, reply handling or other supported fields. Escape customer-provided values before including them in HTML, and keep private account information out of URLs.
Step 4: configure SMTP when your application needs it
Open Developer → SMTP in Yournotify and use the gateway credentials created for your integration.
| Setting | Value |
|---|---|
| SMTP host | smtp.yournotify.com |
| Port | 587 |
| Encryption | TLS; commonly labelled STARTTLS for port 587 |
| Authentication | On |
| Username | Your API name |
| Password | Your API key |
Use the actual credential name and key from your account, not the literal words “API name” and “API key”. Save them in the application’s secure configuration. Set the From address to an approved sender and send one test message from the application’s own test function.
If authentication fails, check the username, key, whitespace and whether the application is connecting to the correct host and port. If authentication succeeds but delivery fails, check sender approval, recipient details and the returned delivery information.
Step 5: connect delivery to the business event
A receipt should follow a confirmed payment, not an unverified browser click. Let the server decide when the event is complete, store the business-event reference and record the resulting email campaign reference.
Use this sequence for a booking application:
- Confirm the booking in your database.
- Record that a confirmation notification is required.
- Send the email through your chosen delivery path.
- Store the result and investigate unclear failures before retrying.
- Give support staff a way to locate the booking and its notification history.
Queueing notifications can help keep the booking page responsive. Your application should also handle temporary failures without sending repeated confirmations for the same booking.
Step 6: measure usefulness as well as delivery
Track delivery failures, bounces and complaints, then investigate the underlying cause. Remove invalid addresses from future promotional audiences and respect communication preferences.
For a transactional journey, measure the action the email supports. A registration email may lead to a booking-page visit; a verification email should lead to successful verification. Open tracking can be affected by email-client behaviour, so combine it with stronger application events rather than treating opens as proof of attention.
For planning, estimate message volume × applicable email rate, then consider the wider workflow your team needs. Check Yournotify pricing against the intended volume and configuration.
Frequently asked questions
Which is better, API or SMTP? Choose the route your application can support cleanly. The API suits structured application integrations; SMTP suits systems already built around SMTP settings.
Can I use the same domain for marketing and transactional email? Plan the domain and sender structure around your traffic and operational needs. Keep message purpose, audience permissions and reporting clear, even where the same organisation owns both streams.
Does an API success response guarantee delivery? No. It confirms acceptance at that stage. Review the subsequent result and test the recipient experience.
Send your first well-tested email
Prepare one sender, one template and one application event. Validate the request, send a controlled test, inspect it on mobile and confirm that the intended action works.
Explore Yournotify Email and open the developer documentation to choose the integration that fits your application.