CDRs

List CDRs (cursor-paginated)

GET

https://partner-api.monta.com

/api/v1/cdrs

Returns a cursor-paginated page of Charge Detail Records (CDRs) for an operator. Use this endpoint to consume CDRs programmatically; for one-shot file delivery by email, use POST /cdr-exports instead.

Pagination:
- The response meta.after is an opaque token. Pass it as the cursor query parameter on the next request to fetch the next page.
- meta.after is null when there are no more pages.
- Page size defaults to 50 and is capped at 100.

Notes:
- The date range may not exceed 90 days.
- If operatorId is omitted, it is derived from the credentials. Consumers with access to multiple operators must specify it explicitly.

Required scope: cdrs:read
Organization authorization: supported

List CDRs (cursor-paginated) › query Parameters

from

string · minLength: 1 · pattern: \d{4}-\d{2}-\d{2} · required

Start of the date range (inclusive), in yyyy-MM-dd format.

Example: 2025-01-01

to

string · minLength: 1 · pattern: \d{4}-\d{2}-\d{2} · required

End of the date range (inclusive), in yyyy-MM-dd format. Must be on or after from, and the range may not exceed 90 days.

Example: 2025-03-31

operatorId

integer | null · int64

The ID of the operator whose CDRs will be returned. If omitted, it is derived from the credentials. Consumers with access to multiple operators must specify it explicitly.

Example: 123

cursor

string | null · maxLength: 1024

Opaque cursor for pagination. Pass the meta.after value from a previous response to fetch the next page. Omit on the first request.

Example: 12345

limit

integer | null · int32 · min: 1 · max: 100

Maximum number of CDRs per page. Defaults to 50 if omitted, capped at 100.

Example: 50

Default: 50

List CDRs (cursor-paginated) › Responses

A page of CDRs

CursorBasedResponse_2

Cdr[] · required

CursorBasedPageMeta · required

CDR Exports Charge Auth Tokens