> ## 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 outreach webhook (backwards compatibility)

> Backwards-compatible alias that proxies to the outreach trigger handler. Authenticated via API key. New integrations should call the canonical `/api/outreach/trigger` endpoint directly; this route is kept so older customer integrations continue to work.



## OpenAPI

````yaml /api-reference/openapi.yaml post /api/webhook/outreach
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/outreach:
    post:
      tags:
        - Webhooks
      summary: Handle outreach webhook (backwards compatibility)
      description: >-
        Backwards-compatible alias that proxies to the outreach trigger handler.
        Authenticated via API key. New integrations should call the canonical
        `/api/outreach/trigger` endpoint directly; this route is kept so older
        customer integrations continue to work.
      operationId: post_webhook_outreach
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/OutreachWebhookRequest'
      responses:
        '200':
          description: >-
            Outreach processed. Same shape as `POST /api/outreach` — the legacy
            webhook route is a thin alias.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/OutreachTriggerResponse'
        '400':
          description: Validation error (missing configurationId, no contact data, etc.)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/WebhookErrorResponse'
        '401':
          description: No API key provided
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/WebhookErrorResponse'
        '404':
          description: Configuration or contact not found for this API key
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/WebhookErrorResponse'
        '500':
          description: Outreach processing failed
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/WebhookErrorResponse'
components:
  schemas:
    OutreachWebhookRequest:
      type: object
      description: Arbitrary outreach payload forwarded to outreach trigger handler
      additionalProperties: true
      example:
        apiKey: tk_live_5f7b1c2e8a1d4e0012c3b4a5
        contact:
          firstName: Alex
          lastName: Morgan
          phoneNumber: '+14165550100'
          email: alex@example.com
        automationId: 5f7b1c2e8a1d4e0012c3b4a5
    OutreachTriggerResponse:
      type: object
      description: >-
        Returned by `POST /api/outreach`. `data` carries resolved IDs the caller
        may need to follow up.
      properties:
        success:
          type: boolean
          enum:
            - true
        message:
          type: string
        data:
          type: object
          properties:
            contactId:
              type: string
            applicationId:
              type: string
            conversationId:
              type: string
            mergeOutcome:
              type: string
              enum:
                - merged
                - created
          additionalProperties: true
      required:
        - success
        - message
      additionalProperties: true
      example:
        success: true
        message: Data processed successfully
        data:
          contactId: 64b2c3d4e5f60012345678aa
          applicationId: 64d2f9c5e8a1d4e001a0b1c2
          conversationId: 64d2f9c5e8a1d4e001a0b1c3
          mergeOutcome: created
    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

````