Telnyx Dynamic Emergency Endpoints API
Dynamic Emergency Endpoints
Dynamic Emergency Endpoints
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
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.curl "https://apis.io/api/v1/apis/telnyx:telnyx-dynamic-emergency-endpoints-api"
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.
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: 3.2.0
info:
title: Telnyx Dynamic Emergency Endpoints 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 Dynamic Emergency Endpoints 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: Dynamic Emergency Endpoints
description: Dynamic Emergency Endpoints
paths:
/dynamic_emergency_endpoints:
get:
summary: List dynamic emergency endpoints
description: Returns the dynamic emergency endpoints according to filters
operationId: ListDynamicEmergencyEndpoints
tags:
- Dynamic Emergency Endpoints
parameters:
- $ref: '#/components/parameters/emergency_PageConsolidated'
- name: filter
in: query
style: deepObject
explode: true
description: 'Consolidated filter parameter (deepObject style). Originally: filter[status], filter[country_code]'
schema:
type: object
properties:
status:
type: string
enum:
- pending
- activated
- rejected
description: Filter by status.
country_code:
type: string
description: Filter by country code.
responses:
'200':
description: Dynamic Emergency Endpoints Responses
content:
application/json:
schema:
type: object
properties:
data:
type: array
items:
$ref: '#/components/schemas/DynamicEmergencyEndpoint'
meta:
$ref: '#/components/schemas/Metadata'
'400':
$ref: '#/components/responses/emergency_BadRequestResponse'
'401':
$ref: '#/components/responses/emergency_UnauthorizedResponse'
'404':
$ref: '#/components/responses/emergency_NotFoundResponse'
'422':
$ref: '#/components/responses/UnprocessableEntity'
'500':
$ref: '#/components/responses/emergency_GenericErrorResponse'
post:
summary: Create a dynamic emergency endpoint
description: Creates a dynamic emergency endpoint, associating a callback number and location with a device for emergency calling.
operationId: CreateDynamicEmergencyEndpoint
tags:
- Dynamic Emergency Endpoints
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/DynamicEmergencyEndpoint'
responses:
'201':
description: Dynamic Emergency Endpoint Response
content:
application/json:
schema:
type: object
properties:
data:
$ref: '#/components/schemas/DynamicEmergencyEndpoint'
'400':
$ref: '#/components/responses/emergency_BadRequestResponse'
'401':
$ref: '#/components/responses/emergency_UnauthorizedResponse'
'404':
$ref: '#/components/responses/emergency_NotFoundResponse'
'422':
$ref: '#/components/responses/UnprocessableEntity'
'500':
$ref: '#/components/responses/emergency_GenericErrorResponse'
servers:
- url: https://api.telnyx.com/v2
description: Version 2.0.0 of the Telnyx API
/dynamic_emergency_endpoints/{id}:
delete:
summary: Delete a dynamic emergency endpoint
description: Deletes the dynamic emergency endpoint based on the ID provided
operationId: DeleteDynamicEmergencyEndpoint
tags:
- Dynamic Emergency Endpoints
parameters:
- name: id
in: path
description: Dynamic Emergency Endpoint id
required: true
schema:
type: string
format: uuid
responses:
'200':
description: Dynamic Emergency Endpoint Response
content:
application/json:
schema:
type: object
properties:
data:
$ref: '#/components/schemas/DynamicEmergencyEndpoint'
'400':
$ref: '#/components/responses/emergency_BadRequestResponse'
'401':
$ref: '#/components/responses/emergency_UnauthorizedResponse'
'404':
$ref: '#/components/responses/emergency_NotFoundResponse'
'422':
$ref: '#/components/responses/UnprocessableEntity'
'500':
$ref: '#/components/responses/emergency_GenericErrorResponse'
get:
summary: Get a dynamic emergency endpoint
description: Returns the dynamic emergency endpoint based on the ID provided
operationId: GetDynamicEmergencyEndpoint
tags:
- Dynamic Emergency Endpoints
parameters:
- name: id
in: path
description: Dynamic Emergency Endpoint id
required: true
schema:
type: string
format: uuid
responses:
'200':
description: Dynamic Emergency Endpoint Response
content:
application/json:
schema:
type: object
properties:
data:
$ref: '#/components/schemas/DynamicEmergencyEndpoint'
'400':
$ref: '#/components/responses/emergency_BadRequestResponse'
'401':
$ref: '#/components/responses/emergency_UnauthorizedResponse'
'404':
$ref: '#/components/responses/emergency_NotFoundResponse'
'422':
$ref: '#/components/responses/UnprocessableEntity'
'500':
$ref: '#/components/responses/emergency_GenericErrorResponse'
servers:
- url: https://api.telnyx.com/v2
description: Version 2.0.0 of the Telnyx API
components:
responses:
emergency_BadRequestResponse:
description: Bad request, the request was unacceptable, often due to missing a required parameter.
content:
application/json:
schema:
$ref: '#/components/schemas/Errors'
example:
errors:
- code: '10015'
title: Bad Request
detail: The request failed because it was not well-formed.
emergency_NotFoundResponse:
description: The requested resource doesn't exist.
content:
application/json:
schema:
$ref: '#/components/schemas/Errors'
example:
errors:
- code: '10005'
title: Resource not found
detail: The requested resource or URL could not be found.
emergency_GenericErrorResponse:
description: Unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/Errors'
example:
errors:
- code: '10007'
title: Unexpected error
detail: An unexpected error occured.
emergency_UnauthorizedResponse:
description: Unauthorized
content:
application/json:
schema:
$ref: '#/components/schemas/Errors'
example:
errors:
- code: '10009'
title: Authentication failed
detail: The required authentication headers were either invalid or not included in the request.
UnprocessableEntity:
description: Unprocessable entity. Check the 'detail' field in response for details.
content:
application/json:
schema:
$ref: '#/components/schemas/Errors'
example:
errors:
- code: '10027'
title: Unprocessable Entity
detail: The server understood the syntax of the request but was unable to process the instructions.
emergency_BadRequestResponse_2:
content:
application/json:
schema:
$ref: '#/components/schemas/emergency_Errors'
description: Bad request, the request was unacceptable, often due to missing a required parameter.
emergency_UnprocessableEntity:
content:
application/json:
schema:
$ref: '#/components/schemas/emergency_Errors'
description: Unprocessable entity. Check the 'detail' field in response for details.
DynamicEmergencyEndpointResponse:
content:
application/json:
schema:
properties:
data:
$ref: '#/components/schemas/DynamicEmergencyEndpoint'
type: object
description: Dynamic Emergency Endpoint Response
emergency_NotFoundResponse_2:
content:
application/json:
schema:
$ref: '#/components/schemas/emergency_Errors'
description: The requested resource doesn't exist.
emergency_GenericErrorResponse_2:
content:
application/json:
schema:
$ref: '#/components/schemas/emergency_Errors'
description: Unexpected error
emergency_UnauthorizedResponse_2:
content:
application/json:
schema:
$ref: '#/components/schemas/emergency_Errors'
description: Unauthorized
listDynamicEmergencyEndpoints:
content:
application/json:
schema:
properties:
data:
items:
$ref: '#/components/schemas/DynamicEmergencyEndpoint'
type: array
meta:
$ref: '#/components/schemas/Metadata'
type: object
description: Dynamic Emergency Endpoints Responses
emergency_UnprocessableEntity_2:
description: Unprocessable entity. Check the 'detail' field in response for details.
content:
application/json:
schema:
$ref: '#/components/schemas/Errors_2'
example:
errors:
- code: '10027'
title: Unprocessable Entity
detail: The server understood the syntax of the request but was unable to process the instructions.
schemas:
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
Errors:
properties:
errors:
type: array
items:
$ref: '#/components/schemas/billing-group_Error'
type: object
DynamicEmergencyEndpoint:
type: object
properties:
id:
type: string
example: 0ccc7b54-4df3-4bca-a65a-3da1ecc777f0
readOnly: true
record_type:
type: string
description: Identifies the type of the resource.
readOnly: true
example: dynamic_emergency_endpoint
dynamic_emergency_address_id:
type: string
description: An id of a currently active dynamic emergency location.
example: 0ccc7b54-4df3-4bca-a65a-3da1ecc777f0
status:
type: string
description: Status of dynamic emergency address
readOnly: true
enum:
- pending
- activated
- rejected
example: pending
sip_from_id:
type: string
example: FXDFWEDF
readOnly: true
callback_number:
type: string
example: '+13125550000'
caller_name:
type: string
example: Jane Doe Desk Phone
created_at:
type: string
description: ISO 8601 formatted date of when the resource was created
readOnly: true
example: '2018-02-02T22:25:27.521Z'
updated_at:
type: string
description: ISO 8601 formatted date of when the resource was last updated
readOnly: true
example: '2018-02-02T22:25:27.521Z'
required:
- dynamic_emergency_address_id
- callback_number
- caller_name
Metadata:
type: object
title: Metadata
properties:
total_pages:
type: number
description: Total number of pages based on pagination settings
example: 13
format: integer
total_results:
type: number
description: Total number of results
example: 13
format: integer
page_number:
type: number
description: Current Page based on pagination settings (included when defaults are used.)
example: 3
format: integer
page_size:
type: number
description: Number of results to return per page based on pagination settings (included when defaults are used.)
example: 1
format: integer
emergency_Error:
properties:
code:
type: string
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
emergency_Errors:
properties:
errors:
items:
$ref: '#/components/schemas/emergency_Error'
type: array
type: object
Errors_2:
properties:
errors:
type: array
items:
$ref: '#/components/schemas/Error'
type: object
Error:
required:
- code
- title
properties:
code:
type: string
x-format: int64
title:
type: string
detail:
type: string
description: A human-readable explanation of the error.
description:
type: string
source:
type: object
properties:
pointer:
description: JSON pointer (RFC6901) to the offending entity.
type: string
format: json-pointer
parameter:
description: Indicates which query parameter caused the error.
type: string
meta:
type: object
additionalProperties: true
example:
title: Invalid street address
source:
pointer: /street_address
code: '20207'
description: The street address provided is invalid.
type: object
parameters:
emergency_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
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