Docs

List User Call Records

Returns call log records filtered by parameters specified.

GET

Query

Arguments
stringrequired

Internal identifier of the RingCentral account. Default value is "~" to indicate that the account associated with current authorization session should be used.

string

Short extension number of a user. If specified, returns call log for this particular extension only. Cannot be combined with `phoneNumber` filter

string

The direction of call records to be included in the result. If omitted, both inbound and outbound calls are returned.

string

The type of call records to be included in the result. If omitted, all call types are returned.

string

Defines the level of details for returned call records.

boolean

Deprecated, replaced with `recordingType` filter, still supported for compatibility reasons. Indicates if only recorded calls should be returned. If both `withRecording` and `recordingType` parameters are specified, then `withRecording` is ignored

string

Indicates that call records with recordings of particular type should be returned. If omitted, then calls with and without recordings are returned.

string

The beginning of the time range to return call records in ISO 8601 format including timezone, for example `2016-03-10T18:07:52.534Z`. The default value is `dateTo` minus 24 hours

string

The end of the time range to return call records in ISO 8601 format including timezone, for example `2016-03-10T18:07:52.534Z`. The default value is current time.

string

Internal identifier of a call session.

string

Internal identifier of a telephony session.

string
boolean

Indicates that deleted calls records should be returned

stringrequired

Internal identifier of the RingCentral extension. Default value is "~" to indicate that the extension associated with current authorization session should be used.

PaginationRequest a specific window of rows with limit and offset. Learn more
number

Maximum number of rows to return.

number

Number of rows to skip.

Field selectionChoose which fields should be included in the response. Learn more
string

Comma-separated response fields to include.

Every app you connect,one REST pattern

Call any app with one REST pattern. MindCloud handles each provider's auth, request shape, and responses for you.

Learn what the Universal API is
One REST patternUse the same request structure across apps like Slack, HubSpot, Salesforce, and thousands more.
Managed connectionsSend a MindCloud connection ID instead of handling provider tokens, refresh logic, and credential storage yourself.
Action-level docsEach action page shows the exact endpoint, required arguments, optional controls, and response behavior for that app version.