In this short tutorial, we'll show you how to track the delivery status of messages you send with Programmable SMS in your Node.js web application. Twilio will notify you about the status of your SMS and MMS messages via a webhook, after which you can log this information or choose to send your delivery data back to Twilio.
Webhooks are user-defined HTTP callbacks. They are usually triggered by some event, such as receiving an SMS message or an incoming phone call. When that event occurs, Twilio makes an HTTP request (usually a POST or a GET) to the URL configured for the webhook.
To handle a webhook, you'll need to build a small web application that can accept HTTP requests.
Webhooks function the same for every Twilio application:
- Twilio makes an HTTP request to a URI that you provide.
- Your application performs whatever logic you feel necessary - read/write from a database, integrate with another API, or perform some computation.
- Your application then replies to Twilio with a TwiML response with the instructions you want Twilio to perform.
Statuses for which you can receive notifications include:
- read (WhatsApp only)
For a full description of these and other message statuses, see the API reference documentation.
To get Twilio to call your webhook, you need to provide a URL to your application in the statusCallback parameter of each message for which you want the status callbacks.
Let's take a look an example of how you can specify this parameter. Typically, you would include a URL that points to your application, but we'll use PostBin so we can debug what Twilio sends your webhook:
Please note: it's okay to hardcode your credentials when testing locally, but you should use environment variables to keep them secret before deploying to production. Check out how to set environment variables for more information.
Next, head over to PostBin and create a new bin. Replace the
statusCallback parameter in the snippet with the URL of your new bin.
When you run the code, you should receive your text message. In addition, you should see at least one request come into your PostBin similar to this:
This request shows the MessageStatus of sent. Assuming all was successful, you should see that followed up by another request with a status of delivered (it may take a few minutes to show up).
Once you get the hang of how the status callback works, you're ready to handle the callback in your own application.
Here's an example of how you might do this by logging the status for each message:
Replying to messages using TwiML? You can still track user actions via callback webhooks.
When you reply to an incoming message with the <Message> verb, you can also provide an action attribute to specify the URL for your callback webhook. The callback can be the same as those explored in the previous sections.
<?xml version="1.0" encoding="UTF-8"?> <Response> <Message action="http://postb.in/b/1234abcd">This message will be tracked!</Message> </Response>
From direct feedback from carrier partners to deliverability data from some larger customers, as well as various other monitoring techniques, Twilio has many sources of data that help optimize overall delivery deliverability. But nothing trumps the live collective data of our customers.
Twilio's Message Feedback API resource enables you to programmatically report back to Twilio critical deliverability information. Actions that indicate a message was received can then be used by Twilio to identify network issues and improve the deliverability of your messages. By looking at both aggregate data and data specific to your account, we have a better chance at improving the delivery of your messages.
Want to learn more? Check out this guide on how to send message delivery feedback to Twilio from your application.