How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Telnyx Call Recordings API

Call Recordings operations.

Telnyx Call Recordings API is one of 169 APIs that Telnyx publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Call Recordings. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 11 operations across 6 paths, and defines 22 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against a single base URL, https://api.telnyx.com/v2.

11 operations 6 paths 22 schemas 3 DELETE5 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://api.telnyx.com/v2
Authentication
HTTP Bearer, HTTP Bearer, OAuth 2.0, HTTP Bearer, HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 6

Telnyx Call Recordings API declares 6 security schemes for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). It accepts HTTP bearer tokens (branded-calling_bearerAuth). It supports OAuth 2.0 (oauthClientAuth) using the authorizationCode and clientCredentials flows, exposing 1 scope. It accepts HTTP bearer tokens (JWT) (outbound-voice-profiles_bearerAuth). It accepts HTTP bearer tokens (pronunciation-dicts_bearerAuth). It accepts HTTP bearer tokens (JWT) (stored-payment-transactions_bearerAuth). By default, every request must be authenticated.

  • branded-calling_bearerAuth — API key passed as a Bearer token in the Authorization header
  • oauthClientAuth — OAuth 2.0 authentication for Telnyx API and MCP integrations
  • pronunciation-dicts_bearerAuth — Telnyx API v2 key. Obtain from https://portal.telnyx.com

Paths & Operations 11

Across 6 paths, the API surfaces 11 operations — 3 DELETE, 5 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Call Recordings 11

Call Recordings operations.

DELETE
/custom_storage_credentials/{connection_id}
Delete a stored credential
DeleteCustomStorageCredentials 1 param → 204401404default
GET
/custom_storage_credentials/{connection_id}
Retrieve a stored credential
GetCustomStorageCredentials 1 param → 200401404default
POST
/custom_storage_credentials/{connection_id}
Create a custom storage credential
CreateCustomStorageCredentials 1 param body → 200401404default
PUT
/custom_storage_credentials/{connection_id}
Update a stored credential
UpdateCustomStorageCredentials 1 param body → 200401404default
GET
/recording_transcriptions
List all recording transcriptions
getRecordingTranscriptions 2 params → 200401404default
DELETE
/recording_transcriptions/{recording_transcription_id}
Delete a recording transcription
deleteRecordingTranscription 1 param → 200401404default
GET
/recording_transcriptions/{recording_transcription_id}
Retrieve a recording transcription
getRecordingTranscription 1 param → 200401404default
GET
/recordings
List all call recordings
GetRecordings 2 params → 200401403404500default
POST
/recordings/actions/delete
Delete a list of call recordings
DeleteRecordings body → 200401404default
DELETE
/recordings/{recording_id}
Delete a call recording
DeleteRecording 1 param → 200401404default
GET
/recordings/{recording_id}
Retrieve a call recording
GetRecording 1 param → 200401404default

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are RecordingResponseData (19 properties), RecordingTranscription (8 properties), call-recordings_Error (5 properties), S3ConfigurationData (5 properties). Each schema is shown below with its type and property counts.

CustomStorageConfiguration
object
2 properties 2 required
AwsSecretAccessKey
string
AWS secret access key.
AwsAccessKeyId
string
AWS credentials access key id.
Region
string
Region where the bucket is located.
S3ConfigurationData
object
5 properties 1 required
RecordType
string
Identifies record type.
Cursor
object
2 properties
GCSConfigurationData
object
3 properties 1 required
AzureAccountKey
string
Azure Blob Storage account key.
call-recordings_Errors
object
1 property
PaginationMeta
object
4 properties
Bucket
string
Name of the bucket to be used to store recording files.
AzureConfigurationData
object
4 properties 1 required
call-recordings_Error
object
5 properties 2 required
RecordingResponse
object
1 property
RecordingTranscription
object
8 properties
ConnectionIdCredentials
string
Uniquely identifies a Telnyx application (Call Control, TeXML) or Sip connection resource.
Credentials
string
Opaque credential token used to authenticate and authorize with storage provider.
AzureAccountName
string
Azure Blob Storage account name.
call-recordings_CursorPaginationMeta
object
3 properties
RecordingResponseData
object
19 properties
CredentialsResponse
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

telnyx-call-recordings-api-openapi.yml Raw ↑

Other APIs Telnyx publishes across the network.

Telnyx Access Tokens API
Telnyx Addresses API
Telnyx Advanced Number Orders API
Telnyx Assistants API
Telnyx Audio API
Telnyx Audit Logs API
Telnyx Authentication Providers API
Telnyx AutoRechargePreferences API
Telnyx Billing API
Telnyx Billing Groups API
Telnyx Brands API
Telnyx Bucket SSL Certificate API
Where this information came from

This is an independent, third-party profile of Telnyx Call Recordings API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.