Telnyx UserAddresses API

Operations for working with UserAddress records. UserAddress records are stored addresses that users can use for non-emergency-calling purposes, such as for shipping addresses for orders of wireless SIMs (or other physical items). They cannot be used for emergency calling and are distinct from Address records, which are used on phone numbers.

GitHub OpenAPI

Operations 6

GET /user/addresses List all user addresses #
POST /user/addresses Creates a user address #
GET /user/addresses/{id} Retrieve a user address #
GET /user_addresses List all user addresses #
POST /user_addresses Creates a user address #
GET /user_addresses/{id} Retrieve a user address #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/telnyx:telnyx-useraddresses-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

telnyx-useraddresses-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Telnyx User Addresses API
  version: 2.0.0
  contact:
    email: support@telnyx.com
  x-endpoint-cost: light
  x-refined-note:
  - x-latency-category differs across the merged source definitions and was not carried
  description: 'Operations tagged UserAddresses across 3 of this provider''s published API definitions: telnyx-openapi.json, telnyx-openapi.yml, telnyx-openapi_2.json. Each path carries the servers of the definition it was published in.'
servers:
- url: https://api.telnyx.com/v2
  description: Version 2.0.0 of the Telnyx API
security:
- bearerAuth: []
tags:
- name: UserAddresses
  description: Operations for working with UserAddress records. UserAddress records are stored addresses that users can use for non-emergency-calling purposes, such as for shipping addresses for orders of wireless SIMs (or other physical items). They cannot be used for emergency calling and are distinct from Address records, which are used on phone numbers.
paths:
  /user/addresses:
    get:
      description: Returns a paginated list of your user addresses, with support for filtering and sorting.
      summary: List all user addresses
      operationId: FindUserAddress
      tags:
      - UserAddresses
      x-endpoint-cost: medium
      parameters:
      - $ref: '#/components/parameters/user-addresses_PageConsolidated'
      - $ref: '#/components/parameters/user-addresses_FilterConsolidated'
      - $ref: '#/components/parameters/SortUserAddress'
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: array
                    items:
                      $ref: '#/components/schemas/UserAddress'
                  meta:
                    $ref: '#/components/schemas/PaginationMeta'
        '400':
          description: Bad request
        '401':
          description: Unauthorized
        '404':
          description: Resource not found
      x-latency-category: responsive
    post:
      description: Creates a new user address from the provided details and returns the created address.
      summary: Creates a user address
      operationId: CreateUserAddress
      tags:
      - UserAddresses
      x-endpoint-cost: medium
      parameters: []
      requestBody:
        description: Parameters that can be defined during user address creation
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/UserAddressCreate'
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    $ref: '#/components/schemas/UserAddress'
        '422':
          description: Bad request
      x-latency-category: responsive
    servers:
    - url: https://api.telnyx.com/v2
      description: Version 2.0.0 of the Telnyx API
  /user/addresses/{id}:
    get:
      description: Retrieves the details of an existing user address.
      summary: Retrieve a user address
      operationId: GetUserAddress
      tags:
      - UserAddresses
      parameters:
      - name: id
        in: path
        description: user address ID
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    $ref: '#/components/schemas/UserAddress'
        '401':
          description: Unauthorized
        '404':
          description: Resource not found
        '422':
          description: Bad request
      x-latency-category: responsive
    servers:
    - url: https://api.telnyx.com/v2
      description: Version 2.0.0 of the Telnyx API
  /user_addresses:
    get:
      description: Returns a paginated list of your user addresses, with support for filtering and sorting.
      summary: List all user addresses
      operationId: FindUserAddress_2
      tags:
      - UserAddresses
      x-endpoint-cost: medium
      parameters:
      - $ref: '#/components/parameters/user-addresses_PageConsolidated_26a215df92'
      - $ref: '#/components/parameters/user-addresses_FilterConsolidated_26a215df92'
      - $ref: '#/components/parameters/SortUserAddress'
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: array
                    items:
                      $ref: '#/components/schemas/user-addresses_UserAddress'
                  meta:
                    $ref: '#/components/schemas/PaginationMeta'
        '400':
          description: Bad request
        '401':
          description: Unauthorized
        '404':
          description: Resource not found
    post:
      description: Creates a new user address from the provided details and returns the created address.
      summary: Creates a user address
      operationId: CreateUserAddress_2
      tags:
      - UserAddresses
      x-endpoint-cost: medium
      parameters: []
      requestBody:
        description: Parameters that can be defined during user address creation
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/user-addresses_UserAddressCreate'
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    $ref: '#/components/schemas/user-addresses_UserAddress'
        '422':
          description: Bad request
    servers:
    - url: https://api.telnyx.com/v2
      description: Version 2.0.0 of the Telnyx API
  /user_addresses/{id}:
    get:
      description: Retrieves the details of an existing user address.
      summary: Retrieve a user address
      operationId: GetUserAddress_2
      tags:
      - UserAddresses
      parameters:
      - name: id
        in: path
        description: user address ID
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    $ref: '#/components/schemas/user-addresses_UserAddress'
        '401':
          description: Unauthorized
        '404':
          description: Resource not found
        '422':
          description: Bad request
    servers:
    - url: https://api.telnyx.com/v2
      description: Version 2.0.0 of the Telnyx API
components:
  schemas:
    user-addresses_phone_number:
      type: string
      description: The phone number associated with the user address.
      example: '+12125559000'
    user-addresses_street_address:
      type: string
      description: The primary street address information about the user address.
      example: 600 Congress Avenue
    user-addresses_neighborhood_26a215df92:
      type: string
      description: The neighborhood of the user address. This field is not used for addresses in the US but is used for some international addresses.
      example: Ciudad de los deportes
    user-addresses_UserAddressCreate:
      type: object
      required:
      - first_name
      - last_name
      - business_name
      - street_address
      - locality
      - country_code
      properties:
        customer_reference:
          $ref: '#/components/schemas/customer_reference'
        first_name:
          $ref: '#/components/schemas/user-addresses_first_name_26a215df92'
        last_name:
          $ref: '#/components/schemas/user-addresses_last_name_26a215df92'
        business_name:
          $ref: '#/components/schemas/user-addresses_business_name_26a215df92'
        phone_number:
          $ref: '#/components/schemas/user-addresses_phone_number_26a215df92'
        street_address:
          $ref: '#/components/schemas/user-addresses_street_address_26a215df92'
        extended_address:
          $ref: '#/components/schemas/user-addresses_extended_address_26a215df92'
        locality:
          $ref: '#/components/schemas/user-addresses_locality_26a215df92'
        administrative_area:
          $ref: '#/components/schemas/user-addresses_administrative_area_26a215df92'
        neighborhood:
          $ref: '#/components/schemas/user-addresses_neighborhood_26a215df92'
        borough:
          $ref: '#/components/schemas/user-addresses_borough_26a215df92'
        postal_code:
          $ref: '#/components/schemas/user-addresses_postal_code_26a215df92'
        country_code:
          $ref: '#/components/schemas/user-addresses_country_code_26a215df92'
        skip_address_verification:
          $ref: '#/components/schemas/skip_address_verification'
    user-addresses_administrative_area:
      type: string
      description: The locality of the user address. For US addresses, this corresponds to the state of the address.
      example: TX
    UserAddressCreate:
      type: object
      required:
      - first_name
      - last_name
      - business_name
      - street_address
      - locality
      - country_code
      properties:
        customer_reference:
          $ref: '#/components/schemas/customer_reference'
        first_name:
          $ref: '#/components/schemas/user-addresses_first_name'
        last_name:
          $ref: '#/components/schemas/user-addresses_last_name'
        business_name:
          $ref: '#/components/schemas/user-addresses_business_name'
        phone_number:
          $ref: '#/components/schemas/user-addresses_phone_number'
        street_address:
          $ref: '#/components/schemas/user-addresses_street_address'
        extended_address:
          $ref: '#/components/schemas/user-addresses_extended_address'
        locality:
          $ref: '#/components/schemas/user-addresses_locality'
        administrative_area:
          $ref: '#/components/schemas/user-addresses_administrative_area'
        neighborhood:
          $ref: '#/components/schemas/user-addresses_neighborhood'
        borough:
          $ref: '#/components/schemas/user-addresses_borough'
        postal_code:
          $ref: '#/components/schemas/user-addresses_postal_code'
        country_code:
          $ref: '#/components/schemas/user-addresses_country_code'
        skip_address_verification:
          $ref: '#/components/schemas/skip_address_verification'
    user-addresses_first_name_26a215df92:
      type: string
      description: The first name associated with the user address.
      example: Alfred
    customer_reference:
      type: string
      description: A customer reference string for customer look ups.
      example: MY REF 001
    user-addresses_last_name_26a215df92:
      type: string
      description: The last name associated with the user address.
      example: Foster
    user-addresses_locality_26a215df92:
      type: string
      description: The locality of the user address. For US addresses, this corresponds to the city of the address.
      example: Austin
    user-addresses_UserAddress:
      type: object
      title: UserAddress
      properties:
        id:
          type: string
          format: uuid
          description: Uniquely identifies the user address.
          example: c3527e69-dc5a-4b3e-8f44-99d209f83c1d
        record_type:
          type: string
          description: Identifies the type of the resource.
          example: user_address
        customer_reference:
          $ref: '#/components/schemas/customer_reference'
        first_name:
          $ref: '#/components/schemas/user-addresses_first_name_26a215df92'
        last_name:
          $ref: '#/components/schemas/user-addresses_last_name_26a215df92'
        business_name:
          $ref: '#/components/schemas/user-addresses_business_name_26a215df92'
        phone_number:
          $ref: '#/components/schemas/user-addresses_phone_number_26a215df92'
        street_address:
          $ref: '#/components/schemas/user-addresses_street_address_26a215df92'
        extended_address:
          $ref: '#/components/schemas/user-addresses_extended_address_26a215df92'
        locality:
          $ref: '#/components/schemas/user-addresses_locality_26a215df92'
        administrative_area:
          $ref: '#/components/schemas/user-addresses_administrative_area_26a215df92'
        neighborhood:
          $ref: '#/components/schemas/user-addresses_neighborhood_26a215df92'
        borough:
          $ref: '#/components/schemas/user-addresses_borough_26a215df92'
        postal_code:
          $ref: '#/components/schemas/user-addresses_postal_code_26a215df92'
        country_code:
          $ref: '#/components/schemas/user-addresses_country_code_26a215df92'
        created_at:
          type: string
          description: ISO 8601 formatted date indicating when the resource was created.
          example: '2018-02-02T22:25:27.521Z'
        updated_at:
          type: string
          description: ISO 8601 formatted date indicating when the resource was updated.
          example: '2018-02-02T22:25:27.521Z'
    user-addresses_locality:
      type: string
      description: The locality of the user address. For US addresses, this corresponds to the city of the address.
      example: Austin
    user-addresses_business_name:
      type: string
      description: The business name associated with the user address.
      example: Toy-O'Kon
    user-addresses_street_address_26a215df92:
      type: string
      description: The primary street address information about the user address.
      example: 600 Congress Avenue
    user-addresses_postal_code_26a215df92:
      type: string
      description: The postal code of the user address.
      example: '78701'
    UserAddress:
      type: object
      title: UserAddress
      properties:
        id:
          type: string
          format: uuid
          description: Uniquely identifies the user address.
          example: c3527e69-dc5a-4b3e-8f44-99d209f83c1d
        record_type:
          type: string
          description: Identifies the type of the resource.
          example: user_address
        customer_reference:
          $ref: '#/components/schemas/customer_reference'
        first_name:
          $ref: '#/components/schemas/user-addresses_first_name'
        last_name:
          $ref: '#/components/schemas/user-addresses_last_name'
        business_name:
          $ref: '#/components/schemas/user-addresses_business_name'
        phone_number:
          $ref: '#/components/schemas/user-addresses_phone_number'
        street_address:
          $ref: '#/components/schemas/user-addresses_street_address'
        extended_address:
          $ref: '#/components/schemas/user-addresses_extended_address'
        locality:
          $ref: '#/components/schemas/user-addresses_locality'
        administrative_area:
          $ref: '#/components/schemas/user-addresses_administrative_area'
        neighborhood:
          $ref: '#/components/schemas/user-addresses_neighborhood'
        borough:
          $ref: '#/components/schemas/user-addresses_borough'
        postal_code:
          $ref: '#/components/schemas/user-addresses_postal_code'
        country_code:
          $ref: '#/components/schemas/user-addresses_country_code'
        created_at:
          type: string
          description: ISO 8601 formatted date indicating when the resource was created.
          example: '2018-02-02T22:25:27.521Z'
        updated_at:
          type: string
          description: ISO 8601 formatted date indicating when the resource was updated.
          example: '2018-02-02T22:25:27.521Z'
    user-addresses_last_name:
      type: string
      description: The last name associated with the user address.
      example: Foster
    user-addresses_first_name:
      type: string
      description: The first name associated with the user address.
      example: Alfred
    user-addresses_borough:
      type: string
      description: The borough of the user address. This field is not used for addresses in the US but is used for some international addresses.
      example: Guadalajara
    user-addresses_phone_number_26a215df92:
      type: string
      description: The phone number associated with the user address.
      example: '+12125559000'
    user-addresses_country_code_26a215df92:
      type: string
      description: The two-character (ISO 3166-1 alpha-2) country code of the user address.
      example: US
    user-addresses_postal_code:
      type: string
      description: The postal code of the user address.
      example: '78701'
    user-addresses_extended_address_26a215df92:
      type: string
      description: Additional street address information about the user address such as, but not limited to, unit number or apartment number.
      example: 14th Floor
    user-addresses_borough_26a215df92:
      type: string
      description: The borough of the user address. This field is not used for addresses in the US but is used for some international addresses.
      example: Guadalajara
    user-addresses_country_code:
      type: string
      description: The two-character (ISO 3166-1 alpha-2) country code of the user address.
      example: US
    user-addresses_business_name_26a215df92:
      type: string
      description: The business name associated with the user address.
      example: Toy-O'Kon
    skip_address_verification:
      type: boolean
      description: An optional boolean value specifying if verification of the address should be skipped or not. UserAddresses are generally used for shipping addresses, and failure to validate your shipping address will likely result in a failure to deliver SIM cards or other items ordered from Telnyx. Do not use this parameter unless you are sure that the address is correct even though it cannot be validated. If this is set to any value other than true, verification of the address will be attempted, and the user address will not be allowed if verification fails. If verification fails but suggested values are available that might make the address correct, they will be present in the response as well. If this value is set to true, then the verification will not be attempted. Defaults to false (verification will be performed).
      default: false
    user-addresses_administrative_area_26a215df92:
      type: string
      description: The locality of the user address. For US addresses, this corresponds to the state of the address.
      example: TX
    user-addresses_extended_address:
      type: string
      description: Additional street address information about the user address such as, but not limited to, unit number or apartment number.
      example: 14th Floor
    PaginationMeta:
      type: object
      properties:
        total_pages:
          type: integer
          example: 3
        total_results:
          type: integer
          example: 55
        page_number:
          type: integer
          example: 2
        page_size:
          type: integer
          example: 25
    user-addresses_neighborhood:
      type: string
      description: The neighborhood of the user address. This field is not used for addresses in the US but is used for some international addresses.
      example: Ciudad de los deportes
  parameters:
    user-addresses_FilterConsolidated_26a215df92:
      name: filter
      in: query
      style: deepObject
      explode: true
      description: 'Consolidated filter parameter (deepObject style). Originally: filter[customer_reference][eq], filter[customer_reference][contains], filter[street_address][contains]'
      schema:
        type: object
        properties:
          customer_reference:
            type: object
            description: Filter user addresses via the customer reference. Supports both exact matching (eq) and partial matching (contains). Matching is not case-sensitive.
            properties:
              eq:
                type: string
                description: Filter user addresses via exact customer reference match. Matching is not case-sensitive.
              contains:
                type: string
                description: If present, user addresses with <code>customer_reference</code> containing the given value will be returned. Matching is not case-sensitive.
          street_address:
            type: object
            description: Filter user addresses via street address. Supports partial matching (contains). Matching is not case-sensitive.
            properties:
              contains:
                type: string
                description: If present, user addresses with <code>street_address</code> containing the given value will be returned. Matching is not case-sensitive. Requires at least three characters.
      examples:
        customer_reference_eq:
          summary: Filter by exact customer reference
          description: Find user addresses with exact customer reference match
          value:
            customer_reference:
              eq: MY REF 001
        customer_reference_contains:
          summary: Filter by partial customer reference
          description: Find user addresses containing part of customer reference
          value:
            customer_reference:
              contains: REF
        street_address_contains:
          summary: Filter by street address
          description: Find user addresses containing part of street address
          value:
            street_address:
              contains: Congress
        combined_filters:
          summary: Combined filters
          description: Use multiple filters together
          value:
            customer_reference:
              contains: REF
            street_address:
              contains: Avenue
    user-addresses_FilterConsolidated:
      name: filter
      in: query
      style: deepObject
      explode: true
      description: 'Consolidated filter parameter (deepObject style). Originally: filter[customer_reference][eq], filter[customer_reference][contains], filter[street_address][contains]'
      schema:
        type: object
        properties:
          customer_reference:
            type: object
            description: Filter user addresses via the customer reference. Supports both exact matching (eq) and partial matching (contains). Matching is not case-sensitive.
            properties:
              eq:
                type: string
                description: Filter user addresses via exact customer reference match. Matching is not case-sensitive.
              contains:
                type: string
                description: If present, user addresses with <code>customer_reference</code> containing the given value will be returned. Matching is not case-sensitive.
          street_address:
            type: object
            description: Filter user addresses via street address. Supports partial matching (contains). Matching is not case-sensitive.
            properties:
              contains:
                type: string
                description: If present, user addresses with <code>street_address</code> containing the given value will be returned. Matching is not case-sensitive. Requires at least three characters.
      examples:
        customer_reference_eq:
          summary: Filter by exact customer reference
          description: Find user addresses with exact customer reference match
          value:
            customer_reference:
              eq: MY REF 001
        customer_reference_contains:
          summary: Filter by partial customer reference
          description: Find user addresses containing part of customer reference
          value:
            customer_reference:
              contains: REF
        street_address_contains:
          summary: Filter by street address
          description: Find user addresses containing part of street address
          value:
            street_address:
              contains: Congress
        combined_filters:
          summary: Combined filters
          description: Use multiple filters together
          value:
            customer_reference:
              contains: REF
            street_address:
              contains: Avenue
    SortUserAddress:
      name: sort
      in: query
      required: false
      description: "Specifies the sort order for results. By default sorting direction is ascending. To have the results sorted in descending order add the <code> -</code> prefix.<br/><br/>\nThat is: <ul>\n  <li>\n    <code>street_address</code>: sorts the result by the\n    <code>street_address</code> field in ascending order.\n  </li>\n\n  <li>\n    <code>-street_address</code>: sorts the result by the\n    <code>street_address</code> field in descending order.\n  </li>\n</ul> <br/> If not given, results are sorted by <code>created_at</code> in descending order."
      schema:
        type: string
        enum:
        - created_at
        - first_name
        - last_name
        - business_name
        - street_address
        example: street_address
        default: created_at
    user-addresses_PageConsolidated_26a215df92:
      name: page
      in: query
      style: deepObject
      explode: true
      description: 'Consolidated page parameter (deepObject style). Originally: page[size], page[number]'
      schema:
        type: object
        properties:
          size:
            type: integer
            minimum: 1
            maximum: 250
            default: 20
            description: The size of the page
          number:
            type: integer
            minimum: 1
            default: 1
            description: The page number to load
    user-addresses_PageConsolidated:
      name: page
      in: query
      style: deepObject
      explode: true
      description: 'Consolidated page parameter (deepObject style). Originally: page[size], page[number]'
      schema:
        type: object
        properties:
          size:
            type: integer
            minimum: 1
            maximum: 250
            default: 20
            description: The size of the page
          number:
            type: integer
            minimum: 1
            default: 1
            description: The page number to load
  responses:
    GetAllUserAddressResponse:
      content:
        application/json:
          schema:
            properties:
              data:
                items:
                  $ref: '#/components/schemas/UserAddress'
                type: array
              meta:
                $ref: '#/components/schemas/PaginationMeta'
            type: object
      description: Successful response
    UserAddressResponse:
      content:
        application/json:
          schema:
            properties:
              data:
                $ref: '#/components/schemas/UserAddress'
            type: object
      description: Successful response
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: API key
      description: 'Telnyx API key supplied as `Authorization: Bearer <token>`. In production, auth may be validated by the API gateway and forwarded via Telnyx auth headers.'
    Payment:
      type: apiKey
      in: header
      name: Authorization
      description: 'Machine Payment Protocol credential used on paid retries, sent as `Authorization: Payment ...`. Obtained by paying a challenge returned in the `WWW-Authenticate` header of a 402 response. This is not a Telnyx API key; initial challenge requests use standard bearer authentication instead.'
    agent-memory_bearerAuth:
      type: http
      scheme: bearer
      description: Telnyx API key
    bearerAuth:
      type: http
      scheme: bearer
    branded-calling_bearerAuth:
      type: http
      scheme: bearer
      description: Telnyx API key. Generate one at https://portal.telnyx.com/#/app/api-keys.
    collections_bearerAuth:
      type: http
      scheme: bearer
      description: Telnyx API key. Collections and results are automatically scoped to the authenticated user's organization.
    number-reputation_bearerAuth:
      type: http
      scheme: bearer
      description: Telnyx API key. Generate one at https://portal.telnyx.com/#/app/api-keys.
    oauthClientAuth:
      type: oauth2
      flows:
        clientCredentials:
          tokenUrl: https://api.telnyx.com/v2/oauth/token
          scopes:
            admin: Administrative access to Telnyx resources
        authorizationCode:
          authorizationUrl: https://api.telnyx.com/v2/oauth/authorize
          tokenUrl: https://api.telnyx.com/v2/oauth/token
          refreshUrl: https://api.telnyx.com/v2/oauth/token
          scopes:
            admin: Administrative access to Telnyx resources
      description: OAuth 2.0 authentication for Telnyx API and MCP integrations
    outbound-voice-profiles_bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
    pronunciation-dicts_bearerAuth:
      type: http
      scheme: bearer
      description: Telnyx API v2 key. Obtain from https://portal.telnyx.com
    rcs-registration_bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: API key
    stored-payment-transactions_bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
    transcriptions-search_bearerAuth:
      type: http
      scheme: bearer
      description: Telnyx API key. Results are automatically scoped to the authenticated user's organization.
    web-search_bearerAuth:
      type: http
      scheme: bearer
      description: Telnyx API key
    pay-connectors_bearerAuth:
      type: http
      scheme: bearer
      description: Telnyx API key, not the processor bearer token.
    telnyxApiKey:
      type: http
      scheme: bearer
      description: Management-only Telnyx account credential.
x-refined-from:
- telnyx-openapi.json
- telnyx-openapi.yml
- telnyx-openapi_2.json
x-service-info:
  categories:
  - communication
  - developer-tools
  docs:
    apiReference: https://developers.telnyx.com
    homepage: https://telnyx.com
    llms: https://telnyx.com/llms.txt