Skip to main content
The telephony schemas handle incoming call webhooks from your telephony provider (e.g., Telnyx). These webhooks trigger the call processing pipeline.

​
IncomingCallWebhook

Received when a new emergency call is initiated.
​
call_control_id
string
required
Unique identifier for controlling the call session. Used for call management operations like answer, transfer, or hang up.
​
to
string
required
Phone number that received the call (the emergency dispatch number)
​
from_
string
required
Phone number of the caller initiating the emergency call
This schema represents the base implementation. Additional fields should be added based on your telephony provider’s webhook specification (e.g., Telnyx, Twilio, etc.).

​
Example

{
  "call_control_id": "v3:T02llQxIyaOgXRGxMl7HkHUsHW6PaNss",
  "to": "+15551234567",
  "from_": "+15559876543"
}

​
Integration notes

The from_ field uses an underscore suffix because from is a reserved keyword in Python.

​
Extending the schema

Depending on your telephony provider, you may want to add additional fields such as:
  • call_session_id: Additional session identifier
  • direction: Call direction (inbound/outbound)
  • state: Current call state (ringing, answered, etc.)
  • start_time: Timestamp when the call was initiated
  • caller_id_name: Caller ID display name if available
  • metadata: Custom metadata attached to the call
Refer to your telephony provider’s documentation for the complete webhook payload specification.
  • CallPacket - Processed call data created from telephony webhooks
  • Queue Item - Queue management for incoming calls

Build docs developers (and LLMs) love

Get started for freeTalk to us