PNTR
All guides

Webhooks guide

Inspect Twilio status callbacks with a persistent endpoint

Twilio status callbacks are informational requests sent as a message moves through delivery states. PNTR can receive and store these callbacks without a local server, making it useful for checking the fields your eventual handler must process.

Explore PNTR's online webhook tester
Create the Twilio endpoint

Status callback URL

https://yourname.pntr.dev/twilio/status

Setup

  1. 1

    Create a status-callback URL

    Create a PNTR hostname with capture enabled and copy a URL such as https://yourname.pntr.dev/twilio/status.

  2. 2

    Attach it to a test message

    Set the message's StatusCallback to the PNTR URL when sending through Twilio, or configure the equivalent callback field for the Twilio product you are testing.

  3. 3

    Send using test-safe recipients

    Send a message only to a recipient you control and follow Twilio's trial or test-account restrictions. Status callbacks may arrive more than once as the message state changes.

  4. 4

    Inspect the encoded fields

    Open the PNTR request log and inspect the application/x-www-form-urlencoded body, message identifiers, status field, error fields when present, and X-Twilio-Signature.

  5. 5

    Move to a verified handler

    In the application endpoint, validate X-Twilio-Signature using the exact requested URL and parameters, respond quickly, and treat status updates as repeatable and potentially out of order.

Before you ship

This workflow is for informational status callbacks. Inbound SMS and voice action webhooks can require a valid TwiML response, which PNTR's fixed capture acknowledgement does not provide.

Primary documentation