> ## 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. # Get an account transfer > Retrieves a specific transfer. For onchain activity, outbound transfers typically appear with an account source and blockchain destination, while inbound transfers typically appear with a blockchain source and account destination. ## OpenAPI ````yaml openapi/accounts.yaml get /v1/accounts/transfers/{id} openapi: 3.0.2 info: version: 1.0.0 title: Accounts (Stablecoin) API description: > Circle's Accounts API provides endpoints for managing stablecoin accounts -- including transfers, withdrawals, deposits, wire and ACH bank accounts, and blockchain addresses. An **Account** is a general representation of a ledger or custody object that holds balances. It can be a business account, a stablecoin account ledger for an end user, an extra sub-ledger, or any future custody solution. license: name: Circle License url: https://circle.com/terms servers: - url: https://api-sandbox.circle.com - url: https://api.circle.com security: [] tags: - name: Accounts description: Manage accounts. - name: Account Groups description: Manage custody account groups and their memberships. - name: Transactions description: | Get a unified, customer-friendly view of account transaction activity. - name: Transfers description: Manage account transfers. - name: Withdrawals description: Manage account bank withdrawals (fiat offramp). - name: Wires description: Manage account bank accounts for wire transfers. - name: ACH description: Manage account bank accounts for ACH transfers. - name: Deposits description: Get information on account bank deposits. - name: Deposit Addresses description: Manage account deposit addresses. - name: Recipient Addresses description: Manage account recipient addresses used for transfers. paths: /v1/accounts/transfers/{id}: get: tags: - Transfers summary: Get an account transfer description: > Retrieves a specific transfer. For onchain activity, outbound transfers typically appear with an account source and blockchain destination, while inbound transfers typically appear with a blockchain source and account destination. operationId: getAccountTransfer parameters: - $ref: '#/components/parameters/IdPath' responses: '200': description: Successfully retrieved a transfer. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: $ref: '#/components/schemas/GetAccountTransferResponse' '401': $ref: '#/components/responses/NotAuthorized' '404': $ref: '#/components/responses/NotFound' '500': $ref: '#/components/responses/InternalServerError' 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: > Circle-generated universally unique identifier (UUID v4). Useful for identifying a specific request when communicating with Circle Support. schema: $ref: '#/components/schemas/XRequestId' schemas: GetAccountTransferResponse: title: GetAccountTransferResponse properties: data: $ref: '#/components/schemas/Transfer' XRequestId: type: string format: uuid example: 2adba88e-9d63-44bc-b975-9b6ae3440dde Transfer: type: object description: A transfer of funds. required: - id - source - destination - amount - status properties: id: $ref: '#/components/schemas/Id' source: $ref: '#/components/schemas/TransferSourceLocation' destination: $ref: '#/components/schemas/TransferDestinationLocation' amount: $ref: '#/components/schemas/Money' fees: description: >- An array of fees applied to a transaction. This is only available when there is at least one non-zero fee. type: array items: $ref: '#/components/schemas/Fee' transactionHash: description: >- A hash that uniquely identifies the onchain transaction. This is only available where either source or destination is of type blockchain. type: string example: '0x4cebf8f90c9243a23c77e4ae20df691469e4b933b295a73376292843968f7a63' status: description: Status of the transfer. type: string enum: - pending - complete - failed errorCode: $ref: '#/components/schemas/TransferErrorCode' policyEvaluation: $ref: '#/components/schemas/PolicyEvaluation' createDate: description: The create date of the transfer. type: string format: date-time Error: type: object required: - code - message properties: code: type: integer description: > Circle internal status code from the platform `CoreStatusCode` enum (and its domain-specific extensions). **This is not the HTTP status code** — `-1` is the catch-all unknown error, `1`/`2` indicate API parameter problems, `3` is forbidden, `4` is unauthorized, and larger values identify domain-specific failures. Consumers should rely on the HTTP status line for transport-level error class and on this field for the specific Circle error case. example: 2 message: type: string description: >- Internal error message; suitable for logging but not for end-user display. example: API parameter invalid. externalMessage: type: string description: > End-user-displayable error message. Present when the server has generated a customer-facing variant for this error; omitted otherwise. example: The provided amount exceeds the maximum allowed. Id: type: string description: Unique system-generated identifier for the entity. format: uuid example: b8627ae8-732b-4d25-b947-1df8f4007a29 TransferSourceLocation: description: A source of funds. oneOf: - $ref: '#/components/schemas/TransferSourceAccountLocation' - $ref: '#/components/schemas/TransferSourceBlockchainLocation' TransferDestinationLocation: description: A destination of funds. oneOf: - $ref: '#/components/schemas/TransferDestinationBlockchainLocation' - $ref: '#/components/schemas/TransferDestinationAccountLocation' Money: 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: type: string description: Currency code for the amount. example: USD enum: - USD - EUR Fee: type: object required: - amount - currency - type properties: amount: type: string description: Magnitude of the fee amount, in units of the currency, with a `.`. example: '10.00' currency: type: string description: Currency code for the amount. enum: - USD type: type: string description: Category of the fee. enum: - network TransferErrorCode: type: string description: >- Indicates the failure reason of a transfer. Only present for transfers in a `failed` state. nullable: true enum: - transfer_failed - transfer_denied - blockchain_error - insufficient_funds - invalid_crypto_address PolicyEvaluation: type: object description: >- Results of policy evaluation. Only present if a policy decision has been recorded. nullable: true required: - status properties: status: description: Status of the policy evaluation. type: string enum: - approved - pending - rejected - expired - cancelled - failed example: approved TransferSourceAccountLocation: description: A source account location. type: object required: - type - id properties: type: type: string enum: - account id: type: string description: The identifier of the source account. example: '1000662322' TransferSourceBlockchainLocation: description: >- A source blockchain location. Only present in transfer responses, not accepted in transfer creation requests. type: object required: - type - chain properties: type: type: string enum: - blockchain chain: $ref: '#/components/schemas/Chain' TransferDestinationBlockchainLocation: description: A destination blockchain address. type: object required: - type - chain - address properties: type: type: string enum: - blockchain address: $ref: '#/components/schemas/Address' addressTag: $ref: '#/components/schemas/AddressTag' chain: $ref: '#/components/schemas/Chain' TransferDestinationAccountLocation: description: A destination account location. type: object required: - type - id properties: type: type: string enum: - account id: type: string description: The identifier of the destination account. example: '1000662322' address: type: string description: > The blockchain address associated with the destination account. Present when the transfer originates from a blockchain source (e.g. a crypto deposit). example: '0xecf270635e22f87b9d9ed501eca86e74caf59623' addressTag: $ref: '#/components/schemas/AddressTag' Chain: type: string description: A blockchain that a given currency is available on. enum: - ALGO - APTOS - ARB - AVAX - BASE - BTC - CELO - CODEX - ETH - HBAR - HYPEREVM - INK - LINEA - NEAR - NOBLE - OP - PLUME - PAH - POLY - SEI - SOL - SONIC - SUI - UNI - WORLDCHAIN - XDC - XLM - XRP - ZKS - ZKSYNC Address: type: string description: > An alphanumeric string representing a blockchain address. Formatting varies by blockchain. Be sure to preserve the exact formatting and capitalization of the address. example: '0x8381470ED67C3802402dbbFa0058E8871F017A6F' AddressTag: type: string description: >- The secondary identifier for a blockchain address. An example of this is the memo field on the Stellar network, which can be text, ID, or hash format. nullable: true example: '123456789' 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: $ref: '#/components/schemas/Error' example: code: 4 message: Unauthorized. NotFound: description: The specified resource was not found. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: $ref: '#/components/schemas/Error' example: code: 404 message: Not found. InternalServerError: description: >- The server encountered an unexpected condition that prevented it from fulfilling the request. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: $ref: '#/components/schemas/Error' example: code: -1 message: 'Something went wrong. errId: 1f0b0c455e40f753f07b4f0ae6abd4b4' securitySchemes: bearerAuth: type: http scheme: bearer ````