CDR Exports

Request a CDR export

POST

https://partner-api.monta.com

/api/v1/cdr-exports

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.

Notes:
- The date range may not exceed 31 days.
- If operatorId is omitted, it is derived from the credentials. Consumers with multiple authorised operators must specify it explicitly.
- direction defaults to INBOUND (CDRs Monta issued as CPO to partner eMSPs). Set OUTBOUND to export CDRs Monta received as eMSP from partner CPOs.

Required scope: cdr-exports:write
Organization authorization: supported

Request a CDR export › Request Body

CdrExportRequest

from

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

Start of the export 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 export range (inclusive), in yyyy-MM-dd format. Must be on or after from, and the range may not exceed 31 days.

Example: 2025-01-31

email

string · email · minLength: 1 · required

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

Example: ops@example.com

operatorId

integer | null · int64

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

Example: 123

format

string · enum

Output format for the exported file. Defaults to CSV.

Enum values:

CSV

JSON

Example: CSV

Default: CSV

emspIdentifier

string | null · maxLength: 10

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

Example: DE*ABC

selfManaged

boolean | null

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

Example: false

direction

string · enum

Direction of the CDRs to export. INBOUND (default) exports CDRs Monta issued as CPO to partner eMSPs (Monta operated the charge point). OUTBOUND exports CDRs Monta received as eMSP from partner CPOs (Monta's drivers charged on partner networks). Defaults to INBOUND when omitted.

Enum values:

INBOUND

OUTBOUND

Example: INBOUND

Default: INBOUND

Request a CDR export › Responses

CDR export accepted; the file will be sent by email

CdrExportAccepted

status

string · required

Export request status. Always queued for an accepted request.

Example: queued

message

string · required

Human-readable confirmation message.

Example: CDR export has been queued and will be sent to ops@example.com

POST/api/v1/cdr-exports

curl https://partner-api.monta.com/api/v1/cdr-exports \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer <token>' \
  --data '{
  "operatorId": 123,
  "from": "2025-01-01",
  "to": "2025-01-31",
  "format": "CSV",
  "email": "ops@example.com",
  "emspIdentifier": "DE*ABC",
  "selfManaged": false,
  "direction": "INBOUND"
}'

Example Request Body

{
  "operatorId": 123,
  "from": "2025-01-01",
  "to": "2025-01-31",
  "format": "CSV",
  "email": "ops@example.com",
  "emspIdentifier": "DE*ABC",
  "selfManaged": false,
  "direction": "INBOUND"
}

json

Example Responses

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

json

application/json

Authentication CDRs