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-siprec-connectors-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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.

GitHub Google LinkedIn

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

OpenAPI Specification

openapi: 3.2.0
info:
  title: Telnyx SIPREC Connectors 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 SIPREC Connectors across 2 of this provider''s published API definitions: telnyx-openapi.yml, telnyx-openapi.json. Each path carries the servers of the definition it was published in.'
servers:
- description: Version 2.0.0 of the Telnyx API
  url: https://api.telnyx.com/v2
security:
- bearerAuth: []
tags:
- description: SIPREC connectors configuration.
  name: SIPREC Connectors
paths:
  /siprec_connectors:
    post:
      description: Creates a new SIPREC connector configuration.
      operationId: createSiprecConnector
      requestBody:
        $ref: '#/components/requestBodies/SiprecConnectorRequest'
      responses:
        '201':
          $ref: '#/components/responses/SiprecConnectorResponseBody'
        '422':
          $ref: '#/components/responses/siprec_UnprocessableEntityResponse'
        default:
          $ref: '#/components/responses/siprec_GenericErrorResponse'
      summary: Create a SIPREC connector
      tags:
      - SIPREC Connectors
      x-latency-category: responsive
    servers:
    - description: Version 2.0.0 of the Telnyx API
      url: https://api.telnyx.com/v2
  /siprec_connectors/{connector_name}:
    delete:
      description: Deletes a stored SIPREC connector.
      operationId: deleteSiprecConnector
      parameters:
      - $ref: '#/components/parameters/SiprecConnectorName'
      responses:
        '204':
          description: The SIPREC connector was deleted successfully.
        '404':
          $ref: '#/components/responses/siprec_NotFoundResponse'
        default:
          $ref: '#/components/responses/siprec_GenericErrorResponse'
      summary: Delete a SIPREC connector
      tags:
      - SIPREC Connectors
      x-latency-category: responsive
    get:
      description: Returns details of a stored SIPREC connector.
      operationId: getSiprecConnector
      parameters:
      - $ref: '#/components/parameters/SiprecConnectorName'
      responses:
        '200':
          $ref: '#/components/responses/SiprecConnectorResponseBody'
        '404':
          $ref: '#/components/responses/siprec_NotFoundResponse'
        default:
          $ref: '#/components/responses/siprec_GenericErrorResponse'
      summary: Retrieve a SIPREC connector
      tags:
      - SIPREC Connectors
      x-latency-category: responsive
    put:
      description: Updates a stored SIPREC connector configuration.
      operationId: updateSiprecConnector
      parameters:
      - $ref: '#/components/parameters/SiprecConnectorName'
      requestBody:
        $ref: '#/components/requestBodies/SiprecConnectorRequest'
      responses:
        '200':
          $ref: '#/components/responses/SiprecConnectorResponseBody'
        '404':
          $ref: '#/components/responses/siprec_NotFoundResponse'
        '422':
          $ref: '#/components/responses/siprec_UnprocessableEntityResponse'
        default:
          $ref: '#/components/responses/siprec_GenericErrorResponse'
      summary: Update a SIPREC connector
      tags:
      - SIPREC Connectors
      x-latency-category: responsive
    servers:
    - description: Version 2.0.0 of the Telnyx API
      url: https://api.telnyx.com/v2
components:
  responses:
    siprec_NotFoundResponse:
      content:
        application/json:
          example:
            errors:
            - code: 404
              detail: The requested resource does not exist
              title: Not Found
          schema:
            $ref: '#/components/schemas/siprec_Errors'
      description: The requested resource does not exist
    siprec_GenericErrorResponse:
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/siprec_Errors'
      description: Unexpected error.
    siprec_UnprocessableEntityResponse:
      content:
        application/json:
          example:
            errors:
            - code: 422
              detail: The request parameters failed validation
              title: Unprocessable Entity
          schema:
            $ref: '#/components/schemas/siprec_Errors'
      description: Unprocessable entity. The request was well-formed but contains semantic errors.
    SiprecConnectorResponseBody:
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/SiprecConnectorResponse'
      description: Return details of the SIPREC connector.
    siprec_siprec_NotFoundResponse:
      description: The requested resource does not exist
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Errors'
          example:
            errors:
            - code: 404
              title: Not Found
              detail: The requested resource does not exist
    siprec_siprec_GenericErrorResponse:
      description: Unexpected error.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Errors'
    siprec_siprec_UnprocessableEntityResponse:
      description: Unprocessable entity. The request was well-formed but contains semantic errors.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Errors'
          example:
            errors:
            - code: 422
              title: Unprocessable Entity
              detail: The request parameters failed validation
  requestBodies:
    SiprecConnectorRequest:
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/SiprecConnector'
      description: The parameters required to create or update a SIPREC connector.
      required: true
  parameters:
    SiprecConnectorName:
      description: Uniquely identifies a SIPREC connector.
      in: path
      name: connector_name
      required: true
      schema:
        type: string
  schemas:
    siprec_Errors:
      properties:
        errors:
          items:
            $ref: '#/components/schemas/siprec_Error'
          type: array
      type: object
    siprec_Error:
      properties:
        code:
          format: int32
          type: integer
        detail:
          type: string
        meta:
          additionalProperties: true
          type: object
        source:
          properties:
            parameter:
              description: Indicates which query parameter caused the error.
              type: string
            pointer:
              description: JSON pointer (RFC6901) to the offending entity.
              type: string
          type: object
        title:
          type: string
      required:
      - code
      - title
      type: object
    SiprecConnector:
      example:
        app_subdomain: my-app
        host: siprec.telnyx.com
        name: my-siprec-connector
        port: 5060
      properties:
        app_subdomain:
          description: Subdomain to route the call when using Telnyx SRS (optional for non-Telnyx SRS).
          example: my-app-domain
          type: string
        host:
          description: Hostname/IPv4 address of the SIPREC SRS.
          example: siprec.telnyx.com
          type: string
        name:
          description: Name for the SIPREC connector resource.
          example: my-siprec-connector
          type: string
        port:
          description: Port for the SIPREC SRS.
          example: 5060
          type: integer
      required:
      - host
      - port
      - name
      title: SIPREC connector configuration
      type: object
    SiprecConnectorResponse:
      properties:
        data:
          properties:
            app_subdomain:
              description: Subdomain to route calls when using Telnyx SRS (optional).
              example: my-app-domain
              type: string
            created_at:
              description: ISO 8601 formatted date/time of creation.
              example: '2024-01-23T18:10:02.574Z'
              type: string
            host:
              description: Hostname/IPv4 address of the SIPREC SRS.
              example: siprec.telnyx.com
              type: string
            name:
              description: Name for the SIPREC connector resource.
              example: siprec-connector
              type: string
            port:
              description: Port for the SIPREC SRS.
              example: 5060
              type: integer
            record_type:
              example: siprec_connector
              type: string
            updated_at:
              description: ISO 8601 formatted date/time of last update.
              example: '2024-01-23T18:10:02.574Z'
              type: string
          title: SIPREC Connector
          type: object
      required:
      - data
      title: SIPREC Connector Response
      type: object
    Errors:
      properties:
        errors:
          type: array
          items:
            $ref: '#/components/schemas/billing-group_Error'
      type: object
    billing-group_Error:
      type: object
      required:
      - code
      - title
      properties:
        code:
          type: integer
          format: int32
        title:
          type: string
        detail:
          type: string
        source:
          type: object
          properties:
            pointer:
              description: JSON pointer (RFC6901) to the offending entity.
              type: string
            parameter:
              description: Indicates which query parameter caused the error.
              type: string
        meta:
          type: object
          properties: {}
          additionalProperties: true
  securitySchemes:
    bearerAuth:
      scheme: bearer
      type: http
    branded-calling_bearerAuth:
      description: API key passed as a Bearer token in the Authorization header
      scheme: bearer
      type: http
    oauthClientAuth:
      description: OAuth 2.0 authentication for Telnyx API and MCP integrations
      flows:
        authorizationCode:
          authorizationUrl: https://api.telnyx.com/v2/oauth/authorize
          refreshUrl: https://api.telnyx.com/v2/oauth/token
          scopes:
            admin: Administrative access to Telnyx resources
          tokenUrl: https://api.telnyx.com/v2/oauth/token
        clientCredentials:
          scopes:
            admin: Administrative access to Telnyx resources
          tokenUrl: https://api.telnyx.com/v2/oauth/token
      type: oauth2
    outbound-voice-profiles_bearerAuth:
      bearerFormat: JWT
      scheme: bearer
      type: http
    pronunciation-dicts_bearerAuth:
      description: Telnyx API v2 key. Obtain from https://portal.telnyx.com
      scheme: bearer
      type: http
    stored-payment-transactions_bearerAuth:
      bearerFormat: JWT
      scheme: bearer
      type: http
    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
    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.
    rcs-registration_bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: API key
    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
x-refined-from:
- telnyx-openapi.yml
- telnyx-openapi.json