> ## 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. # List all account transactions > Searches for transactions across account activity, including deposits, withdrawals, transfers and other activity. Results are returned in descending chronological order. If date parameters are omitted, returns the most recent transactions. ## OpenAPI ````yaml openapi/accounts.yaml get /v1/accounts/transactions 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/transactions: get: tags: - Transactions summary: List all account transactions description: > Searches for transactions across account activity, including deposits, withdrawals, transfers and other activity. Results are returned in descending chronological order. If date parameters are omitted, returns the most recent transactions. operationId: listAccountTransactions parameters: - $ref: '#/components/parameters/AccountId' - $ref: '#/components/parameters/ClientEntityId' - name: isAttributed description: > Filter by whether the transaction activity is attributed to a client entity under the caller. `true` returns activity for client entities under the caller and excludes the caller's direct activity; `false` returns only the caller's direct activity. When `clientEntityId` is provided, `isAttributed=true` scopes results to that specific client entity. in: query required: false schema: type: boolean example: true - name: type description: >- Filter by simplified transaction category. Repeat the parameter to match multiple types. in: query required: false style: form explode: true schema: type: array uniqueItems: true items: $ref: '#/components/schemas/TransactionType' - name: currency description: Filter by transaction currency code. in: query required: false schema: type: string example: USD - $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 transactions. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' Link: description: Cursor-based pagination links for the next and previous pages. schema: type: string content: application/json: schema: $ref: '#/components/schemas/ListAccountTransactionsResponse' '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/NotAuthorized' '404': $ref: '#/components/responses/NotFound' '500': $ref: '#/components/responses/InternalServerError' security: - bearerAuth: [] components: parameters: AccountId: name: accountId description: >- Identifier of the account. Filters results to fetch only resources associated with the specified account. in: query required: false schema: type: string example: '1000565227' ClientEntityId: name: clientEntityId description: >- Identifier of the client entity. Filters results to fetch only resources associated with the specified client entity. in: query required: false schema: type: string format: uuid example: a3f1b2c4-d5e6-7890-abcd-ef1234567890 From: name: from description: >- Queries items created since the specified date-time (inclusive) in ISO 8601 format. in: query required: false schema: $ref: '#/components/schemas/UtcTimestamp' To: name: to description: >- Queries items created before the specified date-time (inclusive) in ISO 8601 format. in: query required: false schema: $ref: '#/components/schemas/UtcTimestamp' 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`. in: query required: false schema: type: string example: def9520a-5280-4089-9b02-3c9ef8fc8514 PageAfter: name: pageAfter description: >- A collection ID value used for pagination. It marks the exclusive beginning of a page. When provided, the collection resource will return the next `n` items after the id, with `n` being specified by `pageSize`. in: query required: false schema: type: string example: bce1e961-bdb8-4983-a9c2-0b3fbc2614cf 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 omitted, the collection will determine the page size itself. in: query required: false schema: type: integer minimum: 1 example: 5 schemas: TransactionType: type: string enum: - deposit - withdrawal - transfer - fx - fee - credit - other example: transfer ListAccountTransactionsResponse: title: ListAccountTransactionsResponse properties: data: type: array items: $ref: '#/components/schemas/Transaction' UtcTimestamp: type: string description: ISO-8601 UTC date/time format. example: '2020-04-10T02:13:30.000Z' XRequestId: type: string format: uuid example: 2adba88e-9d63-44bc-b975-9b6ae3440dde Transaction: type: object description: A unified transaction record for account activity. required: - id - type - status - amount - createDate - updateDate properties: id: $ref: '#/components/schemas/Id' type: $ref: '#/components/schemas/TransactionType' status: description: Status of the transaction. type: string enum: - pending - complete - failed - returned example: complete amount: $ref: '#/components/schemas/Money' destination: description: Destination of funds, when available. type: object nullable: true allOf: - $ref: '#/components/schemas/TransactionDestinationLocation' source: description: Source of funds, when available. type: object nullable: true allOf: - $ref: '#/components/schemas/TransactionSourceLocation' createDate: $ref: '#/components/schemas/UtcTimestamp' updateDate: $ref: '#/components/schemas/UtcTimestamp' 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 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 TransactionDestinationLocation: description: A destination of funds. oneOf: - $ref: '#/components/schemas/TransactionDestinationAccountLocation' - $ref: '#/components/schemas/TransferDestinationBlockchainLocation' - $ref: '#/components/schemas/TransactionFiatLocation' TransactionSourceLocation: description: A source of funds. oneOf: - $ref: '#/components/schemas/TransferSourceAccountLocation' - $ref: '#/components/schemas/TransferSourceBlockchainLocation' - $ref: '#/components/schemas/TransactionFiatLocation' TransactionDestinationAccountLocation: 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' 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' TransactionFiatLocation: type: object description: A fiat transaction location. required: - type - id properties: type: type: string description: The fiat rail associated with the transaction location. enum: - wire example: wire id: $ref: '#/components/schemas/Id' name: type: string description: Human-readable bank account or rail label, when available. example: COMMERZBANK AG ****3000 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' 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' 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 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' 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: $ref: '#/components/schemas/Error' example: code: 2 message: API parameter invalid. 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 ````