/v1/reports). The
following report types cover Managed Payments activity only. They’re separate
from the Circle Mint camt053 daily statement, which isn’t available on Managed
Payments keys.
Report types
Use
camt_managed for CAMT.053 statements on Managed Payments. The Circle
Mint camt053 type isn’t valid on Managed Payments keys. It covers Circle
Mint accounts, not Managed Payments. See CAMT.053 daily
statements for the ISO 20022 XML
structure, which camt_managed shares.Request and download a report
- Request the report with
POST /v1/reports, passingreportType,dateinYYYY-MM-DDformat, andtimeframewhere the type supports it. Circle interpretsdatein your entity’s reporting timezone, not UTC. For example, a Circle SG entity uses Singapore Time (SGT). Circle generates Managed Payments reports on a schedule:- If the report is available, the response is
200 OKwith the reportidand a pre-signeddownloadUrl. - If the report is still being generated, the response is
202 Acceptedwith a reportidand nodownloadUrl.
- If the report is available, the response is
- If the response was
202 Accepted, pollGET /v1/reports/{id}untilstatusisreadyand adownloadUrlis present. - Download the file from
downloadUrlbefore the time given byexpiresAt. CallGET /v1/reports/{id}again to get a fresh URL after it expires. You can also request the report again. Requests are idempotent, so the same parameters return the same report.
expiresAt uses different formats across endpoints. Create (POST /v1/reports) and get-by-ID (GET /v1/reports/{id}) responses return it as an
ISO 8601 timestamp, as in the preceding example. The list endpoint (GET /v1/reports) returns it as epoch milliseconds.