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

# List connector tokens

> List the connector token for each client environment of an agent.

Only environments that already have a connector are returned. Use the PUT endpoint to create one for an environment that is missing.

The connector token is the per-environment credential a telephony or websocket integration presents so PolyAI routes the call to this agent in that environment. SIP integrations pass it as `X-PolyAi-Auth-Token` in the SIP URI and websocket integrations pass it as the `X-PolyAi-Auth-Token` custom parameter. It is not an API key. Treat it as a secret.



## OpenAPI

````yaml api-reference/agents/openapi.json GET /v1/agents/{agentId}/telephony/connector-tokens
openapi: 3.1.0
info:
  title: PolyAI Agents API
  version: 1.0.11
  description: Manage PolyAI agents, telephony, deployments, and real-time configs.
servers:
  - url: https://api.us.poly.ai
    description: US region
  - url: https://api.eu.poly.ai
    description: EU region
  - url: https://api.uk.poly.ai
    description: UK region
  - url: https://api.studio.poly.ai
    description: Studio region
security:
  - polyApiKey: []
paths:
  /v1/agents/{agentId}/telephony/connector-tokens:
    parameters:
      - name: agentId
        in: path
        required: true
        schema:
          type: string
    get:
      tags:
        - Connectors
      summary: List connector tokens
      description: >-
        List the connector token for each client environment of an agent.


        Only environments that already have a connector are returned. Use the
        PUT endpoint to create one for an environment that is missing.


        The connector token is the per-environment credential a telephony or
        websocket integration presents so PolyAI routes the call to this agent
        in that environment. SIP integrations pass it as `X-PolyAi-Auth-Token`
        in the SIP URI and websocket integrations pass it as the
        `X-PolyAi-Auth-Token` custom parameter. It is not an API key. Treat it
        as a secret.
      operationId: listConnectorTokens
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ConnectorTokensResponse'
        '401':
          description: Unauthorized – missing or invalid API key
        '403':
          description: Forbidden – insufficient permissions
components:
  schemas:
    ConnectorTokensResponse:
      description: Connector tokens for every client environment that has one.
      type: object
      properties:
        tokens:
          description: One entry per client environment with a connector
          type: array
          items:
            $ref: '#/components/schemas/ConnectorTokenResponse'
      required:
        - tokens
    ConnectorTokenResponse:
      description: The connector token for one client environment.
      type: object
      properties:
        clientEnv:
          description: Client environment the token routes calls to
          type: string
          enum:
            - sandbox
            - pre-release
            - live
        connectorId:
          description: ID of the connector the token belongs to
          type: string
        token:
          description: >-
            Connector token. Treat as a secret; it grants call access to this
            agent in this environment.
          type: string
      required:
        - clientEnv
        - connectorId
        - token
  securitySchemes:
    polyApiKey:
      type: apiKey
      in: header
      name: X-API-KEY

````