v1

latestOpenAPI 3.0.12026-07-243686491.1 MB
CDR Exports

Request a CDR export

Triggers an asynchronous export of Charge Detail Records (CDRs) for an operator. The export is processed in the background and the resulting file is delivered by email to the address provided. The recipient email must belong to a Monta user with export permission on the target operator.</br></br>Notes:</br>- The date range may not exceed 31 days.</br>- If operatorId is omitted, it is derived from the credentials. Consumers with multiple authorised operators must specify it explicitly.</br>- direction defaults to INBOUND (CDRs Monta issued as CPO to partner eMSPs). Set OUTBOUND to export CDRs Monta received as eMSP from partner CPOs.</br></br>Required scope: cdr-exports:write </br>Organization authorization: supported

post/api/v1/cdr-exports

Request body

operatorIdinteger nullable

The ID of the operator whose CDRs will be exported. If not provided, operator ID will be derived from the used api credentials.

fromstring required

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

tostring required

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

format'CSV' | 'JSON'
emailstring email required

Email address that the export will be delivered to. Must belong to a Monta user with the export permission on the target operator.

emspIdentifierstring nullable

Optional filter. When set, only CDRs whose EMSP identifier ({CountryCode}*{PartyId}) matches are exported. Does not appear as a column in the exported file.

selfManagedboolean nullable

Optional filter. When set, only CDRs with the matching self-managed flag (bilateral agreement) are exported.

direction'INBOUND' | 'OUTBOUND'

Example request

{
  "operatorId": 123,
  "from": "2025-01-01",
  "to": "2025-01-31",
  "email": "ops@example.com",
  "emspIdentifier": "DE*ABC"
}

Response

CDR export accepted; the file will be sent by email

statusstring required

Export request status. Always queued for an accepted request.

messagestring required

Human-readable confirmation message.

Example response

{
  "status": "queued",
  "message": "CDR export has been queued and will be sent to ops@example.com"
}