Transactional, bulk, and template email flows built on the existing AfriRoute API
The public contract already exposes email send, bulk send, template send, status lookup, campaigns, lists, templates, and marketing flows. The portal should package those into a clean developer journey.
Docs mode
Reference and guide
Keep the task clear, the example nearby, and the next step obvious.
Recommended public flow
Start with single-send transactional email, then branch into template email, bulk notifications, and marketing lists only when the developer needs those features.
Keep status lookup, provider delivery behavior, and webhook-driven tracking close to the request examples so email feels like part of the same platform rather than a separate product.
Core endpoints
Portal design rule
Document email as a product workflow: send, check status, subscribe to events, and scale safely. Do not bury developers in campaign or list management details before they can deliver one message successfully.