Keep your business system in charge.
Your application decides which document is ready, who should receive it and whether the communication is appropriate. MMS Express validates the submission, records a message ID and exposes its processing history and recorded outcome.
This is a custom integration through a REST API. It does not mean a named accounting or CRM product has a built-in MMS Express connector.
Example integration
Month-end statement ready
Your application exports a short statement as an image, checks the customer number and submits the image with “Your September statement is attached.” It saves the returned message ID alongside its own statement reference, then checks for the recorded outcome.
Three parts of a reliable integration.
1. Prepare
Export the relevant document content as a supported image. PDF upload and automatic PDF conversion are not supported. Query the current message limits and keep API credentials on your server.
2. Submit
Use POST /api/v1/messages with the sending account's key and a stable idempotency key for the business operation. Save the response before updating your own workflow.
3. Reconcile
Retrieve GET /api/v1/messages/{id} or process supported signed webhook events. Track unresolved results and handle repeated events without repeating business actions.
Acceptance is the start of tracking.
An accepted API request is not a delivery receipt. The current Sent status records submission to the delivery network. The current API does not expose recipient delivery confirmation or a read status. Webhook transport success also means your endpoint accepted an event, not that a customer received a document.
After a timeout, an integration should keep the original idempotency key and unchanged request. Sending again with a new key can create another message. Read the exact replay and error-handling behaviour in the technical reference.
One funding account, separate sending identities.
For a business serving multiple teams or customers, the main account can fund subaccounts from a shared balance. Each integration uses credentials belonging to its sending account. Passing a subaccount selector in a send request is not supported; a parent key is not a substitute for the correct child account key.
Plan for the actual recipient.
Confirm the intended South African recipient services and evaluate your real document layout with permission before depending on it. Message size, device presentation and recipient settings matter. See compatibility guidance and the reliability methodology.
The developer guide includes cURL, C#/.NET, PHP and server-side JavaScript examples, authentication, media options, status retrieval and webhook handling.
Discuss an integration