How an SMS webhook works
When you send an SMS, the carrier reports the status (sent, delivered, failed). SMSGo receives that status and makes an HTTP POST request to the URL you registered, sending the data as JSON.
A webhook is a mechanism for communication between systems where an event in one application automatically triggers the sending of data to a configured URL in another application. Unlike APIs where you must poll, a webhook notifies you when something happens.
A webhook is a mechanism for communication between systems where an event in one application automatically triggers the sending of data to a configured URL in another application. Unlike APIs where you must poll, a webhook notifies you when something happens.
When you send an SMS, the carrier reports the status (sent, delivered, failed). SMSGo receives that status and makes an HTTP POST request to the URL you registered, sending the data as JSON.
The most common statuses are: queued, sending, delivered, failed, and expired. With this data you can update your dashboard, retry, or alert the user.
SMSGo signs webhooks with HMAC-SHA256. Your backend can validate the signature to ensure the payload really came from SMSGo and was not tampered with.
Yes, we recommend HTTPS for security. The endpoint must accept POST requests and respond with a 2xx status.
SMSGo retries delivery several times with backoff. If the endpoint keeps failing, retries are stopped.
Usually you configure one webhook per account, but you can forward events to multiple internal systems from your endpoint.
Yes. Receiving delivery status webhooks is a feature included with SMSGo.
No credit card. No monthly fee. Credits never expire.
Create free account