This webhook uses Telnyx headers (telnyx-timestamp, telnyx-signature-ed25519) that are compatible with Standard Webhooks specification for SDK generation. Custom validation logic can map these to standard webhook-timestamp and webhook-signature equivalents. See https://github.com/standard-webhooks/standard-webhooks for details.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Unix timestamp (seconds since epoch) of when the webhook was sent - compatible with webhook-timestamp Unix timestamp for replay attack prevention
Base64 encoded Ed25519 signature for webhook verification - compatible with webhook-signature Ed25519 signature of timestamp|payload for verification
Show child attributes
The type of event being sent
"number_order.complete"
Unique identifier for the event
"d578b093-a0e7-4b64-b0d3-6b689a6ff170"
ISO 8601 timestamp of when the event occurred
"2025-08-22T16:23:54.496464Z"
Show child attributes
Identifies the connection associated with this phone number.
"346789098765567"
Identifies the messaging profile associated with the phone number.
"abc85f64-5717-4562-b3fc-2c9600"
Identifies the messaging profile associated with the phone number.
"abc85f64-5717-4562-b3fc-2c9600"
Show child attributes
"+19705555098"
Show child attributes
Unique id for a requirement.
"8ffb3622-7c6b-4ccc-b65f-7a3dc0099576"
The value of the requirement, this could be an id to a resource or a string value.
"45f45a04-b4be-4592-95b1-9306b9db2b21"
A customer reference string for customer look ups.
"MY REF 001"
Type of record
"event"
The server must return a HTTP 200, otherwise we will reattempt to deliver the webhook to the failover URL.
Was this page helpful?