> ## 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 SMS status callback

> Status callback posted by Twilio for outbound SMS/MMS as the message transitions through queued / sent / delivered / failed. Updates the corresponding Message document and broadcasts a socket event so the org sees the latest delivery state.



## OpenAPI

````yaml /api-reference/openapi.yaml post /api/webhook/twilio/sms-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/twilio/sms-status:
    post:
      tags:
        - Webhooks
      summary: Handle Twilio SMS status callback
      description: >-
        Status callback posted by Twilio for outbound SMS/MMS as the message
        transitions through queued / sent / delivered / failed. Updates the
        corresponding Message document and broadcasts a socket event so the org
        sees the latest delivery state.
      operationId: post_webhook_twilio_sms_status
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/TwilioSmsStatusRequest'
      responses:
        '200':
          description: Plain-text acknowledgement (Twilio only checks the 2xx status).
          content:
            text/plain:
              schema:
                type: string
                example: OK
        '500':
          description: Status processing failed
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/WebhookErrorResponse'
components:
  schemas:
    TwilioSmsStatusRequest:
      type: object
      properties:
        MessageSid:
          type: string
          description: Twilio-assigned message identifier whose status is being reported.
        MessageStatus:
          type: string
          description: >-
            Delivery state: `queued`, `sent`, `delivered`, `failed`,
            `undelivered`.
        To:
          type: string
          description: Recipient phone number for the outbound message.
        From:
          type: string
          description: Tether-provisioned Twilio number the message was sent from.
        ErrorCode:
          type: string
          description: Twilio error code when delivery failed (e.g. `30003`).
        ErrorMessage:
          type: string
          description: Human-readable error description paired with `ErrorCode`.
      additionalProperties: true
      example:
        MessageSid: SM5f7b1c2e8a1d4e0012c3b4a5
        MessageStatus: delivered
        To: '+14165550100'
        From: '+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

````