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

# Forward telemetry traces to the backend collector

> Accepts an OpenTelemetry-compatible trace payload from a client (browser SDK, mobile, or another service) and forwards it to the backend collector for ingestion. Fire-and-forget: the API returns 202 once the payload is queued; downstream processing failures are not surfaced to the caller.



## OpenAPI

````yaml /api-reference/openapi.yaml post /api/traces
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/traces:
    post:
      tags:
        - Telemetry
      summary: Forward telemetry traces to the backend collector
      description: >-
        Accepts an OpenTelemetry-compatible trace payload from a client (browser
        SDK, mobile, or another service) and forwards it to the backend
        collector for ingestion. Fire-and-forget: the API returns 202 once the
        payload is queued; downstream processing failures are not surfaced to
        the caller.
      operationId: post_traces
      requestBody:
        required: false
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ForwardTracesRequest'
      responses:
        '202':
          description: Traces accepted
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ForwardTracesResponse'
      security: []
components:
  schemas:
    ForwardTracesRequest:
      type: object
      description: >-
        OpenTelemetry trace payload (any shape). The body is forwarded verbatim
        to the configured collector (Axiom) — Tether does not parse it, so any
        OTLP-JSON or vendor-extended structure works.
      additionalProperties: true
      example:
        resourceSpans:
          - resource:
              attributes:
                - key: service.name
                  value:
                    stringValue: tether-web
                - key: service.version
                  value:
                    stringValue: 2026.05.20
            scopeSpans:
              - spans:
                  - traceId: 4bf92f3577b34da6a3ce929d0e0e4736
                    spanId: 00f067aa0ba902b7
                    name: POST /api/messages
                    kind: 3
                    startTimeUnixNano: '1763624641135000000'
                    endTimeUnixNano: '1763624641311000000'
                    attributes:
                      - key: http.status_code
                        value:
                          intValue: 200
    ForwardTracesResponse:
      type: object
      properties:
        status:
          type: string
          enum:
            - accepted
          description: >-
            Always `accepted` — the API queues the payload synchronously and
            returns; downstream collector failures are not surfaced.
      required:
        - status
      additionalProperties: true
      example:
        status: accepted

````