> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tetherai.ca/llms.txt
> Use this file to discover all available pages before exploring further.

# Handle Twilio call status updates

> Status callback posted by Twilio as a call transitions through queued / ringing / in-progress / completed / busy / no-answer / failed. Updates the Call record with final status, duration, and end timestamp and emits a socket event so the agent UI reflects the change.



## OpenAPI

````yaml /api-reference/openapi.yaml post /api/webhook/calls/twilio/status
openapi: 3.0.3
info:
  title: Tether Relay and Tether API
  version: 1.0.0
  description: >-
    Route-derived OpenAPI contract generated from tether-relay backend sources.
    Regenerate with scripts/sync-openapi-from-backend.mjs.
servers:
  - url: https://your-instance.example.com
    description: Production
  - url: http://localhost:2212
    description: Local API service
security: []
tags:
  - name: AI
  - name: Applications
  - name: Approval
  - name: Auth
  - name: Automations
  - name: Calls
  - name: Campaigns
  - name: Contact Analytics
  - name: Contact Metrics
  - name: Contact Notes
  - name: Contacts
  - name: Conversation Monitor
  - name: Conversations
  - name: Departments
  - name: Email
  - name: Escalation Dashboard
  - name: Event Logs
  - name: Google Sheets
  - name: Marketplace
  - name: Messages
  - name: Notification Sounds
  - name: Notifications
  - name: Org Snapshots
  - name: Organizations
  - name: Outreach
  - name: Outreach Metrics
  - name: Outreach Sources
  - name: Pipelines
  - name: Processes
  - name: Prompts
  - name: Reminders
  - name: Sms
  - name: Templates
  - name: Traces
  - name: Training
  - name: Upload
  - name: User Snapshots
  - name: Users
  - name: Vertical
  - name: Webchats
  - name: Webhook
paths:
  /api/webhook/calls/twilio/status:
    post:
      tags:
        - Webhooks
      summary: Handle Twilio call status updates
      description: >-
        Status callback posted by Twilio as a call transitions through queued /
        ringing / in-progress / completed / busy / no-answer / failed. Updates
        the Call record with final status, duration, and end timestamp and emits
        a socket event so the agent UI reflects the change.
      operationId: post_webhook_calls_twilio_status
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/TwilioCallStatusRequest'
      responses:
        '200':
          description: Plain-text acknowledgement (Twilio only checks 2xx).
          content:
            text/plain:
              schema:
                type: string
                example: OK
        '500':
          description: Status processing failed
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/WebhookErrorResponse'
components:
  schemas:
    TwilioCallStatusRequest:
      type: object
      properties:
        CallSid:
          type: string
          description: >-
            Twilio-assigned call identifier (`CA…`) whose status is being
            reported.
        CallStatus:
          type: string
          description: >-
            Final or transitional state: `queued`, `ringing`, `in-progress`,
            `completed`, `busy`, `no-answer`, `failed`.
        CallDuration:
          type: string
          description: >-
            Total call duration in seconds (as a string), populated when the
            call ends.
        Duration:
          type: string
          description: >-
            Per-leg duration in seconds as Twilio reports it; usually mirrors
            `CallDuration` for single-leg dials.
        From:
          type: string
          description: Calling party phone number in E.164.
        To:
          type: string
          description: Called party phone number in E.164.
      additionalProperties: true
      example:
        CallSid: CA5f7b1c2e8a1d4e0012c3b4a5
        CallStatus: completed
        CallDuration: '42'
        Duration: '1'
        From: '+14165550100'
        To: '+12362320246'
    WebhookErrorResponse:
      type: object
      description: >-
        Error envelope used across provider webhook routes. Most failures only
        carry `error`; a few (ElevenLabs tool errors, ingress validation) add
        `success:false`, `message`, or a `code`. Many of these endpoints respond
        200 with `success:false` for recoverable cases (especially the
        ElevenLabs server tools) — only hard failures use 4xx/5xx.
      properties:
        error:
          type: string
        message:
          type: string
        success:
          type: boolean
          enum:
            - false
        code:
          type: string
        details:
          description: Optional diagnostic detail (stack snippet, validation issues, etc.).
      additionalProperties: true
      example:
        error: Webhook processing failed

````