Request a report
Submits a report generation request. reportType specifies the type of report and required fields.
Supported report types: camt053, camt_managed, managed_payout_transactions, managed_payment_wallet_balances, and managed_payin_transactions. The managed-payment reports take a timeframe field (daily or monthly); camt_managed and managed_payment_wallet_balances support daily only.
If ready, returns 200 with a pre-signed downloadUrl. If not, returns 202 with status pending. Poll GET /v1/reports/{id} for status, or download using GET /v1/reports/{id}/content when ready.
Requests are idempotent: the same entity and request parameters always produce the same report ID. Retries return the existing report. camt053 reports are only returned for accounts with activity in the preceding 365 days.
camt_managed reports are only generated for dates with managed payment activity. Requesting a date with no activity returns 400 ({"code":2,"message":"API parameter invalid"}), the same response as a malformed request. To discover which dates have reports before calling this endpoint, use GET /v1/reports?reportType=camt_managed&startDate=<start>&endDate=<end>.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
Request body for generating a report. The reportType field determines the
type of report and which additional fields are required.
Response
Report is ready. Use the pre-signed downloadUrl to download the file.
Metadata for a unified report. status reflects whether the generated file is available.
If status is ready, the response includes a pre-signed downloadUrl. If pending, generation is still in progress. Poll GET /v1/reports/{id} until ready, then download using GET /v1/reports/{id}/content.
Requests are idempotent: the same entity and request parameters always produce the same report ID. Subsequent POST requests return the existing report.