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
Identifies the type of the resource.
event "event"
The type of event being delivered.
conference.floor.changed "conference.floor.changed"
Identifies the type of resource.
"0ccc7b54-4df3-4bca-a65a-3da1ecc777f0"
Show child attributes
Call Control ID of the new speaker.
"v3:MdI91X4lWFEs7IgbBEOT9M4AigoY08M0WWZFISt1Yw2axZ_IiE4pqg"
Call Control App ID (formerly Telnyx connection ID) used in the call.
"7267xxxxxxxxxxxxxx"
Call Leg ID of the new speaker.
"428c31b6-7af4-4bcb-b7f5-5013ef9657c1"
Call Session ID of the new speaker.
"428c31b6-abf3-3bc1-b7f4-5013ef9657c1"
State received from a command.
"aGF2ZSBhIG5pY2UgZGF5ID1d"
Conference ID that had a speaker change event.
"428c31b6-abf3-3bc1-b7f4-5013ef9657c1"
ISO 8601 datetime of when the event occurred.
"2018-02-02T22:25:27.521Z"
The server must return an HTTP 200, otherwise we will reattempt delivery at the failover webhook URL.
Was this page helpful?