Hosted Number Order Event
Webhook fired when a messaging hosted number order is created, updated, deleted, or progresses through the internal-transfer lifecycle (detected, approval requested, approved, rejected, auto-approved). Inspect event_type to distinguish events.
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.
Headers
Unix timestamp for replay attack prevention
Unix timestamp (seconds since epoch) of when the webhook was sent - compatible with webhook-timestamp
Ed25519 signature of timestamp|payload for verification
Base64 encoded Ed25519 signature for webhook verification - compatible with webhook-signature
Payload
Example payload
{
"data": {
"event_type": "messaging_hosted_numbers_orders.internal_transfer_approval_requested",
"id": "bf6307bd-884d-4c1f-b6ea-c62b8c495d3c",
"occurred_at": "2026-04-20T18:10:02.574Z",
"payload": {
"approval_deadline": 1714521600,
"decision": "pending",
"numbers": [
{
"status": "pending",
"value": "+13125550001"
}
],
"order_id": "0ccc7b54-4df3-4bca-a65a-3da1ecc777f0",
"order_status": "pending",
"profile_id": "d0b1dabe-efdb-4bc8-9dd3-11f0d8b5f5b3",
"user_id": "b448f9cc-a842-4784-98e9-03c1a5872950"
},
"record_type": "event"
}
}Response
The server must return an HTTP 200, otherwise we will reattempt delivery at the failover webhook URL.