How inbound email becomes application data

Create a receiving address through the MailAfrica API, then configure a sending address or domain to route mail to it. Inbound addresses can use the shared platform domain or a domain you control.

A receiving address is an integration endpoint. MailAfrica does not expose it as an IMAP, POP, or webmail mailbox.

When real email arrives, MailAfrica parses common message data such as sender, recipient, subject, headers, text, HTML, and attachments. Your application can fetch the stored message through the inbound API and apply its own business rules.

This means an email can enter an existing service workflow without a person copying details out of a mailbox.

Configure an HTTPS endpoint for an inbound address. MailAfrica sends a signed event when a message arrives and keeps a delivery history. Failed deliveries are retried through a durable outbox.

Verify the HMAC-SHA256 signature using the webhook secret before trusting or processing the event. Use the API documentation for the current header names and payload schema.

A webhook handler should verify the signature, validate the expected event, and acknowledge promptly. Move slower work into your own job queue, and make processing idempotent so a retried notification does not repeat a side effect.

Treat attachments and HTML as untrusted input. Store only what the workflow needs and apply your own retention and access controls.