> ## 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.

# Trigger outreach processing for a lead

> Public endpoint authenticated via API key in Authorization header. Accepts lead data and processes it through the configured lead management pipeline.



## OpenAPI

````yaml /api-reference/openapi.yaml post /api/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/outreach:
    post:
      tags:
        - Outreach
      summary: Trigger outreach processing for a lead
      description: >-
        Public endpoint authenticated via API key in Authorization header.
        Accepts lead data and processes it through the configured lead
        management pipeline.
      operationId: post_outreach
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/OutreachTriggerRequest'
      responses:
        '200':
          description: Outreach processed successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/OutreachTriggerResponse'
        '400':
          description: >-
            Validation error (missing configurationId, no contact data, inactive
            config, etc.)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/OutreachErrorResponse'
        '401':
          description: No API key provided or invalid
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/OutreachErrorResponse'
        '404':
          description: Configuration or contact not found for this API key
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/OutreachErrorResponse'
        '500':
          description: Failed to process outreach
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/OutreachErrorResponse'
      security:
        - bearerAuth: []
components:
  schemas:
    OutreachTriggerRequest:
      type: object
      properties:
        phoneNumber:
          type: string
          description: >-
            Lead phone number; normalized to E.164 server-side. Required unless
            `contactId`/`_id`/`id` is supplied.
        email:
          type: string
          description: Lead email; normalized to lowercase.
        firstName:
          type: string
          description: Lead first name used when creating a new contact.
        lastName:
          type: string
          description: Lead last name used when creating a new contact.
        name:
          type: string
          description: >-
            Single-field display name fallback when `firstName`/`lastName` are
            not supplied.
        contactId:
          type: string
          description: >-
            Contact `_id` for an existing contact; bypasses the create-or-merge
            lookup.
        _id:
          type: string
          description: >-
            Contact `_id` for an existing contact; bypasses the create-or-merge
            lookup.
        id:
          type: string
          description: >-
            Contact `_id` for an existing contact; bypasses the create-or-merge
            lookup.
      description: >-
        Lead data payload. Accepts arbitrary additional fields that are mapped
        to contact dynamic properties.
      additionalProperties: true
      example:
        firstName: Jamie
        lastName: Lee
        phoneNumber: '+14155550133'
        email: jamie.lee@example.com
        source: Facebook Lead Ad
    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
    OutreachErrorResponse:
      type: object
      description: Error envelope returned by `/api/outreach`.
      properties:
        success:
          type: boolean
          enum:
            - false
        message:
          type: string
        error:
          type: string
          description: Stack/detail string for 500 paths.
      required:
        - success
        - message
      additionalProperties: true
      example:
        success: false
        message: Configuration is inactive and cannot process outreach requests
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT

````