> ## 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.

# Get a deposit by ID

> Returns a deposit by ID.



## OpenAPI

````yaml openapi/account.yaml get /v1/businessAccount/deposits/{id}
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/businessAccount/deposits/{id}:
    get:
      tags:
        - Deposits
      summary: Get a deposit by ID
      description: Returns a deposit by ID.
      operationId: getBusinessDepositById
      parameters:
        - $ref: '#/components/parameters/IdPath'
        - name: type
          description: Filters results to get only deposits made by this specific type.
          in: query
          schema:
            type: string
            enum:
              - wire
        - name: walletId
          description: >-
            The wallet ID to which the deposits were made. If not provided, the
            default is the main wallet of the account.
          in: query
          required: false
          schema:
            type: string
      responses:
        '200':
          description: Successfully retrieved a deposit.
          headers:
            X-Request-Id:
              $ref: '#/components/headers/XRequestId'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BusinessDeposit'
              examples:
                response:
                  value:
                    id: b8627ae8-732b-4d25-b947-1df8f4007a29
                    sourceWalletId: 9b57048d-2365-4ff5-956b-0199170d1035
                    destination:
                      type: wallet
                      id: '12345'
                    amount:
                      amount: '3.14'
                      currency: USD
                    fee:
                      amount: '3.14'
                      currency: USD
                    status: pending
                    riskEvaluation:
                      decision: approved
                      reason: '3000'
                    customerExternalRef: EXT01ABSJKDKASJHDS922
                    createDate: '2020-04-10T02:13:30.000Z'
                    updateDate: '2020-04-10T02:13:30.000Z'
                    source:
                      type: wire
                      id: b8627ae8-732b-4d25-b947-1df8f4007a29
                      name: COMMERZBANK AG ****3000
                    fromAmount:
                      amount: '3.14'
                      currency: USD
                    fees:
                      amount: '3.14'
                      currency: USD
                    externalRef: b8627ae8-732b-4d25-b947-1df8f4007a29
                    trackingRef: CIR37N5FXJ
        '401':
          $ref: '#/components/responses/NotAuthorized'
        '404':
          $ref: '#/components/responses/NotFound'
      security:
        - bearerAuth: []
components:
  parameters:
    IdPath:
      name: id
      description: Universally unique identifier (UUID v4) of a resource.
      in: path
      required: true
      schema:
        type: string
        format: uuid
        example: b3d9d2d5-4c12-4946-a09d-953e82fae2b0
  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:
    BusinessDeposit:
      type: object
      description: A deposit
      required:
        - id
        - destination
        - amount
        - status
        - createDate
      properties:
        id:
          $ref: '#/components/schemas/Id'
        sourceWalletId:
          type: string
          description: >-
            The identifier for the bank account where the funds were deposited
            from.
          format: uuid
          example: 9b57048d-2365-4ff5-956b-0199170d1035
        destination:
          $ref: '#/components/schemas/WalletLocation'
        amount:
          $ref: '#/components/schemas/FiatMoney'
        fee:
          $ref: '#/components/schemas/FiatMoneyUsd'
        status:
          type: string
          description: >-
            Status of the deposit. Status `pending` indicates that the deposit
            is in the process of running; `complete` indicates it finished
            successfully; `failed` indicates it failed.
          enum:
            - pending
            - complete
            - failed
        riskEvaluation:
          $ref: '#/components/schemas/RiskEvaluation'
        customerExternalRef:
          $ref: '#/components/schemas/InstitutionalCustomerExternalRef'
        createDate:
          $ref: '#/components/schemas/UtcTimestamp'
        updateDate:
          $ref: '#/components/schemas/UtcTimestamp'
        source:
          $ref: '#/components/schemas/WireDestinationResponse'
        fromAmount:
          $ref: '#/components/schemas/FiatMoneyUsd'
        fees:
          $ref: '#/components/schemas/FiatMoneyUsd'
        externalRef:
          $ref: '#/components/schemas/Id'
          description: The external reference associated with the deposit.
        trackingRef:
          type: string
          description: Tracking reference used for making the deposit.
          example: CIR37N5FXJ
    Id:
      type: string
      description: Unique system generated identifier for the entity.
      format: uuid
      example: b8627ae8-732b-4d25-b947-1df8f4007a29
    WalletLocation:
      type: object
      required:
        - type
        - id
      properties:
        type:
          type: string
          enum:
            - wallet
        id:
          type: string
          description: The id of the wallet.
          example: '12345'
    FiatMoney:
      type: object
      required:
        - amount
        - currency
      properties:
        amount:
          type: string
          description: Magnitude of the amount, in units of the currency, with a `.`.
          example: '3.14'
        currency:
          $ref: '#/components/schemas/FiatCurrency'
    FiatMoneyUsd:
      type: object
      required:
        - amount
        - currency
      properties:
        amount:
          type: string
          description: Magnitude of the amount, in units of the currency, with a `.`.
          example: '3.14'
        currency:
          description: Currency code.
          type: string
          enum:
            - USD
    RiskEvaluation:
      type: object
      description: >-
        Results of risk evaluation. Present when the payment's risk decision is
        `denied` or `review`. Absent when `decision` is `approved` or when no
        risk evaluation was performed.
      nullable: true
      properties:
        decision:
          description: Enumerated decision of the account.
          type: string
          enum:
            - approved
            - denied
            - review
        reason:
          description: >-
            Risk reason code for the decision. Known values include `3000`
            (transaction involves a sanctioned or unsupported wallet) and `2151`
            (transaction denied on outbound compliance screening; a failed
            refund, for example). Present when `decision` is `denied`; may be
            omitted for `review` decisions.
          type: string
          nullable: true
          example: '3000'
    InstitutionalCustomerExternalRef:
      type: string
      description: >-
        A reference to the external customer which is in the memo field of the
        fiat transfer.
      pattern: ^(EXT[A-Z0-9]{18}).$
      example: EXT01ABSJKDKASJHDS922
    UtcTimestamp:
      type: string
      description: ISO-8601 UTC date/time format.
      example: '2020-04-10T02:13:30.000Z'
    WireDestinationResponse:
      type: object
      required:
        - type
        - id
      properties:
        type:
          type: string
          enum:
            - wire
        id:
          $ref: '#/components/schemas/Id'
        name:
          type: string
          description: Bank name plus last four digits of the bank account number or IBAN.
          example: COMMERZBANK AG ****3000
    FiatCurrency:
      type: string
      description: Currency code.
      title: Currency
      enum:
        - USD
        - EUR
        - MXN
        - SGD
        - BRL
  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.
    NotFound:
      description: The specified resource was not found.
      headers:
        X-Request-Id:
          $ref: '#/components/headers/XRequestId'
      content:
        application/json:
          schema:
            type: object
            title: NotFound
            required:
              - code
              - message
            properties:
              code:
                type: integer
                example: 400
              message:
                type: string
                example: Something went wrong.
            example:
              code: 404
              message: Not found.
          examples:
            response:
              value:
                code: 404
                message: Not found.
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer

````