> ## 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 all credit repayments > Returns a paginated list of all repayments (fiat and crypto). Filterable by create date range, transfer ID, type, and status. ## OpenAPI ````yaml openapi/credit.yaml get /v1/credit/repayments openapi: 3.0.2 info: version: ${version} title: Credit API description: > The Circle Credit API provides access to credit facilities including Line of Credit and Settlement Advance products. **Line of Credit** enables direct drawdowns with auto-approval and asynchronous disbursement. Supports both fiat and crypto repayment. **Settlement Advance** requires a reserve-then-request flow with manual approval. Requires wire proof upload for disbursement approval. Supports fiat repayment only. servers: - url: https://api-sandbox.circle.com - url: https://api.circle.com security: [] tags: - name: Credit description: Get credit line details. - name: Credit Transfers description: Create, reserve, and manage credit transfers (drawdowns). - name: Credit Fees description: View fees charged on credit transfers. - name: Credit Repayments description: View and initiate repayments on credit transfers. paths: /v1/credit/repayments: get: tags: - Credit Repayments summary: List all credit repayments description: >- Returns a paginated list of all repayments (fiat and crypto). Filterable by create date range, transfer ID, type, and status. operationId: listCreditRepayments parameters: - $ref: '#/components/parameters/CreditRepaymentTransferId' - $ref: '#/components/parameters/CreditRepaymentType' - $ref: '#/components/parameters/CreditRepaymentStatus' - $ref: '#/components/parameters/From' - $ref: '#/components/parameters/To' - $ref: '#/components/parameters/PageBefore' - $ref: '#/components/parameters/PageAfter' - $ref: '#/components/parameters/PageSize' responses: '200': description: Successfully retrieved a list of credit repayments. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: title: ListCreditRepaymentsResponse properties: data: type: array items: $ref: '#/components/schemas/CreditRepayment' examples: Credit Repayments: value: data: - id: c3d4e5f6-a7b8-9012-cdef-123456789012 transferId: b3d9d2d5-4c12-4946-a09d-953e82fae2b0 repaymentAccountId: be913bbd-83a9-4777-a924-5388f70ffe8b amountApplied: amount: '50450.00' currency: USD paymentAmount: amount: '50450.00' currency: USD type: fiat status: completed settlementDate: '2024-04-10T09:30:00.000Z' createDate: '2024-04-10T09:30:00.000Z' updateDate: '2024-04-10T09:30:00.000Z' '401': $ref: '#/components/responses/NotAuthorized' security: - bearerAuth: [] components: parameters: CreditRepaymentTransferId: name: transferId description: Filters repayments by the associated transfer ID. in: query required: false schema: type: string format: uuid CreditRepaymentType: name: type description: Filters repayments by type. in: query required: false schema: type: string enum: - fiat - crypto CreditRepaymentStatus: name: status description: Filters repayments by their current status. in: query required: false schema: type: string enum: - pending - completed - failed From: name: from description: Queries items created since the specified date-time (inclusive). in: query required: false schema: type: string format: date-time example: '2020-04-10T02:13:30.000Z' To: name: to description: Queries items created before the specified date-time (inclusive). in: query required: false schema: type: string format: date-time example: '2020-04-10T02:13:30.000Z' 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: CreditRepayment: type: object description: A repayment applied to a credit transfer. required: - id - transferId - amountApplied - paymentAmount - type - status - settlementDate - createDate - updateDate properties: id: description: Unique identifier of the repayment. type: string format: uuid example: b3d9d2d5-4c12-4946-a09d-953e82fae2b0 transferId: description: Identifier of the transfer this repayment is applied to. type: string format: uuid example: fc988ed5-c129-4f70-a064-e5beb7eb8e32 repaymentAccountId: description: >- Identifier of the fiat account the repayment was made to. Pass this to `GET /v1/credit/repaymentAccounts/{fiatAccountId}` to retrieve the bank account details. Provided for fiat repayments; omitted for crypto repayments. type: string format: uuid example: be913bbd-83a9-4777-a924-5388f70ffe8b amountApplied: $ref: '#/components/schemas/FiatMoneyUsd' description: The amount applied toward the transfer's outstanding balance. paymentAmount: $ref: '#/components/schemas/FiatMoneyUsd' description: The total payment amount received. type: description: The type of repayment. type: string enum: - fiat - crypto example: fiat status: description: Current status of the repayment. type: string enum: - pending - completed - failed example: completed settlementDate: $ref: '#/components/schemas/UtcTimestamp' description: ISO-8601 UTC date/time when the repayment was settled. createDate: $ref: '#/components/schemas/UtcTimestamp' description: ISO-8601 UTC date/time when the repayment record was created. updateDate: $ref: '#/components/schemas/UtcTimestamp' description: ISO-8601 UTC date/time when the repayment record was last updated. FiatMoneyUsd: type: object required: - amount - currency properties: amount: description: Magnitude of the amount, in units of the currency, with a `.`. type: string example: '3.14' currency: description: Currency code. type: string enum: - USD UtcTimestamp: type: string description: ISO-8601 UTC date/time format. example: '2020-04-10T02:13:30.000Z' responses: 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. securitySchemes: bearerAuth: type: http scheme: bearer ````