Reference
BetaSDKsGet startedTalk to salesSign inSupportStatusPricing
Start typing to search…

Get recordings list by date range

get https://rest-ww.telesign.com/v2/call_recording

Retrieve a list of recordings by date range. Each record includes a reference ID that you can use with other Recordings actions.

General requirements

  • Authentication: Basic
  • Protocols: HTTPS
  • Encoding: Accepts only UTF-8 unicode characters as inputs.
  • Responds with: application/json
  • Required headers: Content-Type - application/json
  • Rate limit: Default rate limits by product
Log in to see full request history
Query Params
string

A timestamp defining the beginning of the date range (inclusive). If you include this, you must also include the end_date_time param, and must not include token.

string

A timestamp defining the end of the date range (inclusive). If you include this, you must also include the start_date_time param, and must not include token.

string
length ≤ 100

The number of records to return per page.

string

Indicates to the service at which page of records to begin retrieval. Found in your previous request to the API. If you include this, you must not include either the start_date_time or the end_date_time params.

Responses

Response body
object
call_recordings
object
string

Specifies the Telesign Voice call for which you want to retrieve or delete recordings.

string

The name of this call record file. If the recording is still in progress, this property does not appear.

string

The status of the recording. Possible values are:
recording - The call recording is still in progress. It is not yet available for retrieval.
 available - The call recording is complete and available for retrieval.
* deleted - The call recording has been deleted and is not available for retrieval.

string

The UTC+0 date when the recording was created. It follows this format: {YYYY}-{MM}-{DD}T{hh}:{mm}:{ss}.

string

An arbitrary string you can include in your next request to the API, to return the next page of results.

400

Bad Request. Your request contains invalid parameters, contains mutually exclusive parameters, or is missing required parameters. If you included start_date_time and end_date_time, check that their values were in proper UTC format, and that token was not included. If you included token, check that its value was a valid token from a previous request to this API, and that start_date_time and end_date_time were not included.

401

Unauthorized. Customer ID and/or API Key were not provided or were not valid.

404

Not Found. No records were found matching the details of your request.

Updated about 1 year ago

Did this page help you?
Language
Credentials
:

Updated about 1 year ago

Did this page help you?
© 2025 Telesign / Terms & Conditions / Privacy Notice / Privacy Hub