SMS API
Connect appointment confirmations and customer follow-up to Mango9 text messaging.
In the CRM: Settings → Developer APIs → SMS API
Send from the business number
SMS API lets a server-side integration submit a message through the account’s messaging setup. Use it for a requested follow-up, an appointment confirmation or another customer conversation supported by the business process.
Telnyx is your carrier. Connect the account, buy or assign the business numbers, and complete the applicable number and messaging setup before sending. The integration must use a sender available to the Mango9 account.
Submit the current request format
Send an HTTPS POST to /smsapi/sms/post on the same server where the account signs in. The current handler reads form-encoded fields. Use application/x-www-form-urlencoded or form data; do not send a raw JSON body.
The legacy GET sending endpoint is disabled. Use the POST fields below even if an older example elsewhere still shows a GET URL.
| Field | What it means |
|---|---|
| key | The saved account API secret. |
| type | Use text for an ordinary SMS or mms for a multimedia message. |
| contacts | Recipient numbers including country codes, separated by commas when submitting more than one. |
| senderid | The sender number or sender ID approved for the account’s route. |
| msg | The message text. Required for type=text. |
| media | The media URL for a multimedia message. Required for type=mms. |
| time / time_zone | Optional scheduled date/time and its city-based time zone, for example America/Los_Angeles. Supply the time zone when scheduling. |
Connect your template to the message
Choose a clear template for the business task, such as a consultation confirmation or a follow-up after a quote. Fill its placeholders with the correct customer and appointment details before submitting the resulting text as msg.
This endpoint expects the message text; it does not take an SMS template ID. Workflows and the normal messaging screens provide their own template choices. Keep those flows aligned so the customer receives one intended confirmation.
Check submission and delivery separately
- Start with one recipient number you control and a sender assigned to this account.
- Submit the message once and read the entire response. Keep the returned messageid, shoot_id and destination when provided.
- Check the message’s activity and delivery status in Mango9. A sent submission response is not proof that the handset received it.
- Confirm that a reply appears in the conversation or the chosen incoming-message integration.
- Before retrying an uncertain request, check for the original message so the customer does not receive duplicates.
Resolve common setup problems
| What you see | What to check |
|---|---|
| Missing parameter | Use key, type, contacts, senderid and the required msg or media field. |
| Invalid or inactive key | Use the saved full secret, the correct Mango9 server and an account enabled for API use. |
| Sender or recipient rejected | Confirm the assigned sender route and recipient number format. |
| IP is not whitelisted | Have the account’s integration access reviewed for the address of the sending server. |
| Insufficient credits | Review the account balance and messaging costs. |
| Scheduled message needs a time zone | Send time_zone with the scheduled time; use a city name such as America/Los_Angeles. |
Plan the conversation after sending
Use SMS Inbox API when another system needs incoming replies. Its callback editor is on the Incoming SMS Callback tab. The callback setting belongs to the account, so coordinate changes with anyone already receiving messages there.
For staff conversations, the Mango9 Windows and iPhone apps let the team continue the exchange. Templates keep the wording consistent while the conversation remains attached to the customer.