> ## Documentation Index > Fetch the complete documentation index at: https://developers.circle.com/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Before reading these docs, install the relevant Circle Skill to get pre-loaded context — skills are LLM-optimized and cover architecture decisions, correct flows, and common pitfalls. In Claude Code: run /plugin marketplace add circlefin/skills then /plugin install circle-skills@circle. With Vercel Skills CLI: run npx skills add circlefin/skills. Available skills: use-usdc https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-usdc/SKILL.md (balances, transfers, approvals on EVM and Solana); EURC has no skill — see https://developers.circle.com/stablecoins/what-is-eurc.md; bridge-stablecoin https://github.com/circlefin/skills/blob/master/plugins/circle/skills/bridge-stablecoin/SKILL.md (crosschain transfers via CCTP, USDC, EURC, and third-party assets); use-arc https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-arc/SKILL.md (Arc chain config, contract deployment, USDC bridging — Arc docs: https://docs.arc.io/llms.txt); use-circle-wallets https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-circle-wallets/SKILL.md (choose wallet type); use-developer-controlled-wallets https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-developer-controlled-wallets/SKILL.md (custodial wallets for payouts and treasury); use-user-controlled-wallets https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-user-controlled-wallets/SKILL.md (embedded wallets with Web2 login); use-modular-wallets https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-modular-wallets/SKILL.md (smart contract wallets with passkeys and ERC-4337); use-gateway https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-gateway/SKILL.md (unified USDC balance, nanopayments); use-smart-contract-platform https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-smart-contract-platform/SKILL.md (deploy, interact, monitor contracts). Pair any skill with the Circle MCP server for live SDK signatures, contract addresses, and chain IDs: {"mcpServers":{"circle":{"url":"https://api.circle.com/v1/codegen/mcp"}}}. > Read the product overview first. Each product has an overview explaining when and why to use it. Read it before quickstarts. > Pick the right wallet type. Developer-controlled (you hold keys), user-controlled (end user holds keys via PIN/social login), or modular (smart contract wallets with passkeys). See https://developers.circle.com/wallets.md. > Use CCTP V2 for crosschain transfers. CCTP natively transfers USDC and EURC via burn-and-mint, and supports permissionless wrapping of third-party assets via lock-and-mint. V1 is legacy; always use V2 unless V1 is specified or the chain requires it (Noble, Sui, and Aptos still require V1). Migration guide: https://developers.circle.com/cctp/migration-from-v1-to-v2.md. > Use Bridge Kit for frontend bridging. Wraps CCTP with a simpler SDK for user-facing apps. Use CCTP directly for backend transfers. > Gas Station vs Paymaster. Gas Station sponsors gas for Circle Wallet transactions. Paymaster lets users pay gas in USDC. Different use cases — read both overviews. > Gateway Nanopayments for sub-cent payments. Gasless USDC micropayments down to $0.000001 via x402 and batched settlement. For pay-per-request APIs, AI agent payments, streaming. > Look up USDC addresses per chain. Never hardcode — use https://developers.circle.com/stablecoins/usdc-contract-addresses.md. > Prefer SDKs over raw API calls. Node.js and Python SDKs handle auth, retries, and errors. > API key required. Bearer token in Authorization header. Testnet and mainnet use separate keys and may use different base URLs depending on the product. > Set up webhooks when available. Most operations are async. Webhooks deliver transaction confirmations and state changes. > When calling list endpoints, paginate using pageSize and pageAfter until no nextPageAfter cursor is returned—stopping at the first page silently misses records. > Building an AI agent? Start with the Agent Stack—Circle CLI, agent wallets, and nanopayments built for autonomous use cases: https://developers.circle.com/agent-stack.md. # List reports > Returns a paginated list of the account's previously generated reports for a given report type and date range, each with a pre-signed `downloadUrl`. Listable report types: `managed_payout_transactions`, `managed_payment_wallet_balances`, `managed_payin_transactions`, `camt_managed`, `camt053`, `camt052`, and `daily_statement_csv`. Note: `camt052` reports are generated on demand, so a `camt052` request returns only the dates previously requested with `POST /v1/reports`. A date that was never requested is absent from the list. Note: the `id` of each listed report is a storage object key, not the deterministic report UUID. It cannot be passed to `GET /v1/reports/{id}` or `GET /v1/reports/{id}/content`; download a listed report using its `downloadUrl`. ## OpenAPI ````yaml openapi/account.yaml get /v1/reports openapi: 3.0.2 info: version: ${version} title: Core Functionality description: > All of Circle's APIs share a common set of core functionality that lets you manage your Circle Account in a programmatic way. With a Circle Account your business can deposit traditional money from 80+ countries and seamlessly convert them into "digital currency dollars": USDC. You can then use USDC for everyday payments and treasury flows. servers: - url: https://api-sandbox.circle.com - url: https://api.circle.com security: [] tags: - name: Balances description: Get information on settled and unsettled balances. - name: Payouts description: Create and get information on 1st party payouts. - name: Wires description: >- Create, get instructions, and get information on 1st party bank accounts for wire transfers. - name: CUBIX description: Create and get information on CUBIX accounts. - name: PIX description: Create and get information on PIX accounts. - name: Transfers description: Create and get information on 1st party transfers. - name: Addresses description: Generate and get information on blockchain addresses. - name: Deposits description: Get information on 1st party deposits. - name: Payments description: Create, cancel, refund, and get updates on card payments. - name: Settlement Bank Routing description: View and manage settlement bank routing preferences for fiat accounts. - name: Reporting description: >- Retrieve transaction and balance reports, including ISO 20022 (CAMT.053) statements and managed-payment reports. paths: /v1/reports: get: tags: - Reporting summary: List reports description: > Returns a paginated list of the account's previously generated reports for a given report type and date range, each with a pre-signed `downloadUrl`. Listable report types: `managed_payout_transactions`, `managed_payment_wallet_balances`, `managed_payin_transactions`, `camt_managed`, `camt053`, `camt052`, and `daily_statement_csv`. Note: `camt052` reports are generated on demand, so a `camt052` request returns only the dates previously requested with `POST /v1/reports`. A date that was never requested is absent from the list. Note: the `id` of each listed report is a storage object key, not the deterministic report UUID. It cannot be passed to `GET /v1/reports/{id}` or `GET /v1/reports/{id}/content`; download a listed report using its `downloadUrl`. operationId: listReports parameters: - name: reportType description: Report type to list. in: query required: true schema: type: string enum: - managed_payout_transactions - managed_payment_wallet_balances - managed_payin_transactions - camt_managed - camt053 - camt052 - daily_statement_csv example: managed_payout_transactions - name: startDate description: > Start of the date range to list (inclusive), formatted as `YYYY-MM-DD`. Must be in the past and on or before `endDate`. in: query required: true schema: type: string format: date example: '2025-01-01' - name: endDate description: > End of the date range to list (inclusive), formatted as `YYYY-MM-DD`. Must be in the past or present and on or after `startDate`. in: query required: true schema: type: string format: date example: '2025-01-31' - name: timeframe description: > Filters results to a single aggregation window. When omitted, reports of all timeframes are returned. in: query required: false schema: type: string enum: - daily - monthly example: daily - $ref: '#/components/parameters/PageBefore' - $ref: '#/components/parameters/PageAfter' - $ref: '#/components/parameters/PageSize' responses: '200': description: Successfully retrieved a list of reports. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: title: ListReportsResponse properties: data: type: array items: $ref: '#/components/schemas/ReportMetadata' example: data: - id: >- managed_payout_transactions/8c3a2f5e-1d4b-4a9c-bf21-6e0d7c9a1b23/2025-01-15/report.csv reportType: managed_payout_transactions timeframe: daily reportDate: '2025-01-15' downloadUrl: https://s3.amazonaws.com/... expiresAt: 1736953200000 - id: >- camt_managed/8c3a2f5e-1d4b-4a9c-bf21-6e0d7c9a1b23/2025-01-15/camt_managed_2025-01-15_report.xml reportType: camt_managed timeframe: daily reportDate: '2025-01-15' downloadUrl: https://s3.amazonaws.com/... expiresAt: 1736953200000 - id: >- camt053/8c3a2f5e-1d4b-4a9c-bf21-6e0d7c9a1b23/2025-01-15/camt053_2025-01-15_report.xml reportType: camt053 timeframe: daily reportDate: '2025-01-15' downloadUrl: https://s3.amazonaws.com/... expiresAt: 1736953200000 - id: >- daily_statement_csv/8c3a2f5e-1d4b-4a9c-bf21-6e0d7c9a1b23/2025-01-15/daily_statement_csv_2025-01-15_report.csv reportType: daily_statement_csv timeframe: daily reportDate: '2025-01-15' downloadUrl: https://s3.amazonaws.com/... expiresAt: 1736953200000 '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/NotAuthorized' '403': $ref: '#/components/responses/Forbidden' '422': $ref: '#/components/responses/UnprocessableEntity' '500': $ref: '#/components/responses/InternalServerError' security: - bearerAuth: [] components: parameters: PageBefore: name: pageBefore description: > A collection ID value used for pagination. It marks the exclusive end of a page. When provided, the collection resource will return the next `n` items before the id, with `n` being specified by `pageSize`. The items will be returned in the natural order of the collection. The resource will return the first page if neither `pageAfter` nor `pageBefore` are specified. SHOULD NOT be used in conjuction with pageAfter. in: query required: false schema: type: string PageAfter: name: pageAfter description: > A collection ID value used for pagination. It marks the exclusive begin of a page. When provided, the collection resource will return the next `n` items after the id, with `n` being specified by `pageSize`. The items will be returned in the natural order of the collection. The resource will return the first page if neither `pageAfter` nor `pageBefore` are specified. SHOULD NOT be used in conjuction with pageBefore. in: query required: false schema: type: string PageSize: name: pageSize description: > Limits the number of items to be returned. Some collections have a strict upper bound that will disregard this value. In case the specified value is higher than the allowed limit, the collection limit will be used. If avoided, the collection will determine the page size itself. in: query required: false schema: type: integer minimum: 1 example: 5 headers: XRequestId: description: >- Universally unique identifier (UUID v4) for the request. Helpful for identifying a request when communicating with Circle support. schema: type: string format: uuid example: 2adba88e-9d63-44bc-b975-9b6ae3440dde schemas: ReportMetadata: type: object description: > Metadata for a single report returned by the list endpoint (`GET /v1/reports`). This shape differs from the per-report `ReportRecord`: the `id` here is the storage object key for the file, not the deterministic report UUID, and therefore **cannot** be passed to `GET /v1/reports/{id}` or `GET /v1/reports/{id}/content`. To download a listed report, use its `downloadUrl` directly. required: - id - reportType - reportDate properties: id: type: string description: > Identifier of the report file. This is the storage object key, not the deterministic report UUID used by the per-report endpoints. It cannot be used with `GET /v1/reports/{id}`; download the report via `downloadUrl`. example: >- managed_payout_transactions/8c3a2f5e-1d4b-4a9c-bf21-6e0d7c9a1b23/2025-01-15/report.csv reportType: type: string enum: - managed_payout_transactions - managed_payment_wallet_balances - managed_payin_transactions - camt_managed - camt053 - camt052 - daily_statement_csv description: Report type identifier. example: managed_payout_transactions timeframe: type: string enum: - daily - monthly description: Aggregation window the report covers. example: daily reportDate: type: string description: | Date the report covers. Daily reports are formatted as `YYYY-MM-DD`; monthly reports are formatted as `YYYY-MM`. example: '2025-01-15' downloadUrl: type: string format: uri description: Pre-signed URL to download the report file. example: https://s3.amazonaws.com/... expiresAt: type: integer format: int64 description: > Expiration time of `downloadUrl`, expressed as milliseconds since the Unix epoch. This list-response field differs from `ReportRecord.expiresAt`, which is an ISO 8601 timestamp in create and get-by-ID responses. example: 1736953200000 responses: BadRequest: description: The request cannot be processed due to a client error. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: type: object title: BadRequest required: - code - message properties: code: type: integer example: 400 message: type: string example: Something went wrong. example: code: 400 message: Bad request. examples: response: value: code: 400 message: Bad request. NotAuthorized: description: >- The request has not been applied because it lacks valid authentication credentials. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: type: object title: NotAuthorized required: - code - message properties: code: type: integer example: 400 message: type: string example: Something went wrong. example: code: 401 message: Malformed authorization. examples: response: value: code: 401 message: Malformed authorization. Forbidden: description: >- The request provides authentication, but the authenticated user does not possess sufficient permissions for accessing this resource. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: type: object title: Forbidden required: - code - message properties: code: type: integer example: 400 message: type: string example: Something went wrong. example: code: 3 message: Forbidden examples: response: value: code: 3 message: Forbidden UnprocessableEntity: description: >- One or more query parameters could not be parsed (such as a malformed date or an unknown value). headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: type: object title: UnprocessableEntity required: - code - message properties: code: type: integer example: 400 message: type: string example: Something went wrong. example: code: 422 message: Invalid value for query parameter 'startDate'. examples: response: value: code: 422 message: Invalid value for query parameter 'startDate'. InternalServerError: description: Unexpected server error. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: type: object title: InternalServerError required: - code - message properties: code: type: integer example: 400 message: type: string example: Something went wrong. example: code: 500 message: Internal server error. examples: response: value: code: 500 message: Internal server error. securitySchemes: bearerAuth: type: http scheme: bearer ````