To learn more about our API, visit the API documentation
Depending on your account, you will have access to either the HTTP API or the MM7 API.
There are four different categories for HTTP API: Messaging, Email, Wallet, and Account. Within each category, there are GET examples for each specific API at the bottom of the API settings page.
For more information on HTTP API, visit the HTTP API page on the API documentation.
For more information on MM7 API, visit the MM7 API page on the API documentation.
Contact us to activate the API settings on your account.
You can get more information on all the API in the API documentation.
An HTTP request is sent either through a GET request or an XML POST request.
No, you may use standard HTTP but we highly recommend that you use HTTPS.
Yes, you can via PostBack notifications. You can receive notifications when someone subscribes or unsubscribes from a campaign. You can also receive notifications upon message receipts or delivery confirmations.
SMS/MMS MT DLR is for delivery receipts. If you turn these PostBacks on, we will notify you when a message is sent and delivered to an end user.
Stuck MMS messages are messages that the system was unable to process and send. Stuck SMS messages are messages that the system was unable to process the first time and again after the retry period of 5 minutes. Stuck SMS messages may become unstuck during subsequent retries.
Stuck messages indicate there may be some issues such as unreachable gateway server, parse error/sending execution terminated, data missing, or missing/unreachable pass/dynamic image/custom content. The stuck message will be cleared after the queue is cleaned up in 3 days.