> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anchorage.com/llms.txt
> Use this file to discover all available pages before exploring further.

# List deposit attributions

> Permissions required: **Read Deposit Attribution** or **Deposit Attribution**

Returns all Deposit Attributions for an Organization based on the provided query parameters. Default sort order is ascending by createdAt.



## OpenAPI

````yaml /knowledge-base/openapi/v4.yaml get /deposit-attributions/attributions
openapi: 3.1.0
info:
  title: Anchorage Digital Account APIs (v4)
  version: 4.0.0-beta
  description: >-
    Reference for the Anchorage Digital v4 API, the surface behind Crypto as a
    Service: account management (accounts and the account tree, beneficiaries,
    freeze/unfreeze/close), balances and transactions, trusted destinations,
    orders and allocations, withdrawals, deposit instructions, deposit
    attributions, the policy engine (policies, approval keys), and supported
    asset types. Approval groups, endorsements, compliance profiles, customers
    (onboarding), fee configuration updates, interest enrollment, funding
    allocations, and destination removal are under construction and return
    mocked data only.


    Status: BETA. The v4 API is available in the sandbox only
    (https://api.anchorage-staging.com/v4) and is not available in production
    yet. The contract may change until general availability. Which endpoints are
    live, in final testing, or under construction:
    https://docs.anchorage.com/platform/developers/caas/caas-overview


    Authentication: every request carries an `Api-Access-Key` header. Every
    POST, PATCH, and DELETE additionally requires an `Idempotency-Key`, and is
    signed with `Api-Signature` (hex-encoded Ed25519 over
    `timestamp_epoch_seconds + uppercase(http_method) + request_path +
    request_body`) plus `Api-Timestamp` (unix epoch seconds).


    Pagination: list endpoints accept `after` (cursor) and `limit` (page size, 1
    to 1000, default 100) and return a `page.endCursor` to continue from. Errors
    use a common envelope with a human-readable `message`; batch endpoints
    return a result per item instead.


    Guides: https://docs.anchorage.com/platform/developers/caas/caas-overview
servers:
  - url: https://api.anchorage-staging.com/v4
security:
  - Api-Access-Key: []
tags:
  - name: Accounts
  - name: Compliance Profiles
  - name: Balances
  - name: Transactions
  - name: Trusted Destinations
  - name: Orders & Allocations
  - name: Withdrawals
  - name: Deposit Instructions
  - name: Deposit Attributions
  - name: Policies
  - name: Approval Groups
  - name: Endorsements
  - name: Customers
  - name: Asset Types
paths:
  /deposit-attributions/attributions:
    get:
      tags:
        - Deposit Attributions
      summary: List deposit attributions
      description: >-
        Permissions required: **Read Deposit Attribution** or **Deposit
        Attribution**


        Returns all Deposit Attributions for an Organization based on the
        provided query parameters. Default sort order is ascending by createdAt.
      operationId: listDepositAttributions
      parameters:
        - in: query
          description: >-
            When paginating this is used to provide the starting point for the
            page to fetch (retrieved from the previous response body)
          name: after
          schema:
            type: string
            minLength: 1
        - in: query
          name: limit
          schema:
            maximum: 1000
            default: 100
            type: integer
            format: int64
            minimum: 1
          description: Maximum number of results to return per query
        - name: status
          in: query
          required: false
          schema:
            type: string
            enum:
              - ATTRIBUTED
              - PENDING
              - UNDER_REVIEW
              - BLOCKED
              - NON_ATTRIBUTABLE
              - INITIATED
          description: Filter by pending or attributed deposits.
        - name: startDateTime
          description: >-
            The start date-time (exclusive) of the deposit attribution process
            in UTC following [RFC
            3339](https://datatracker.ietf.org/doc/html/rfc3339#section-5.6)
            'date-time' format. A valid format example is
            `2021-01-01T00:00:00.000000Z`.
          in: query
          required: false
          schema:
            type: string
            format: date-time
            example: '2019-01-02T12:34:56.000Z'
        - name: endDateTime
          description: >-
            The end date-time (exclusive) to consider the start of the deposit
            attribution process in UTC following [RFC
            3339](https://datatracker.ietf.org/doc/html/rfc3339#section-5.6)
            'date-time' format. A valid format example is
            `2021-01-01T00:00:00.000000Z`.
          in: query
          required: false
          schema:
            type: string
            format: date-time
            example: '2019-01-02T12:34:56.000Z'
        - name: attributedAtStartDateTime
          description: >-
            The start date-time (exclusive) to consider the attribution date of
            the deposit in UTC following [RFC
            3339](https://datatracker.ietf.org/doc/html/rfc3339#section-5.6)
            'date-time' format. A valid format example is
            `2021-01-01T00:00:00.000000Z`.
          in: query
          required: false
          schema:
            type: string
            format: date-time
            example: '2019-01-02T12:34:56.000Z'
        - name: attributedAtEndDateTime
          description: >-
            The end date-time (exclusive) to consider the attribution date of
            the deposit in UTC following [RFC
            3339](https://datatracker.ietf.org/doc/html/rfc3339#section-5.6)
            'date-time' format. A valid format example is
            `2021-01-01T00:00:00.000000Z`.
          in: query
          required: false
          schema:
            type: string
            format: date-time
            example: '2019-01-02T12:34:56.000Z'
        - name: accountIds
          in: query
          required: false
          style: form
          explode: false
          schema:
            type: array
            items:
              type: string
              format: uuid
              example: 3486b413-93d3-4447-afce-2b9c9dc34a32
          description: >-
            Filter results to deposits associated with the specified accounts.
            Multiple values may be provided.
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                type: object
                required:
                  - data
                  - page
                properties:
                  data:
                    type: array
                    items:
                      $ref: '#/components/schemas/DepositAttribution'
                  page:
                    $ref: '#/components/schemas/Page'
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
        '401':
          description: Unauthenticated
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
        '403':
          description: Forbidden
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
        '429':
          description: Too Many Requests
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
components:
  schemas:
    DepositAttribution:
      title: Deposit Attribution
      type: object
      properties:
        depositTransactionId:
          type: string
          pattern: ^[0-9A-Fa-f]+$
          description: >-
            The 32-character hexadecimal transactionId where the transactionType
            is `DEPOSIT`
          example: 0e2b2f9d8d104f1e960b28567255045f
        status:
          description: The status of the Deposit Attribution process
          type: string
          enum:
            - ATTRIBUTED
            - PENDING
            - UNDER_REVIEW
            - BLOCKED
            - NON_ATTRIBUTABLE
            - INITIATED
        sourceAddresses:
          type: array
          description: The source addresses of the deposit transaction.
          items:
            type: string
          example:
            - '0xb4Bb4E3D7f35ede58d99F5e2b8B04f7AC87f9c88'
            - '0x974CaA59e49682CdA0AD2bbe82983419A2ECC400'
        createdAt:
          description: >-
            The system timestamp of when the deposit attribution process
            started. Date-times are always in UTC [RFC
            3339](https://datatracker.ietf.org/doc/html/rfc3339#section-5.6)
            with microsecond precision (e.g `2021-01-01T00:00:00.000000Z`).
          type: string
          format: date-time
          example: '2023-09-12T11:01:07.953571Z'
        attributedAt:
          description: >-
            The system timestamp of when the deposit was attributed. Date-times
            are always in UTC [RFC
            3339](https://datatracker.ietf.org/doc/html/rfc3339#section-5.6)
            with microsecond precision (e.g `2021-01-01T00:00:00.000000Z`). Can
            be null if the deposit is not attributed.
          type: string
          format: date-time
          example: '2023-07-27T21:16:44.124798Z'
        attributionType:
          type: string
          description: >-
            The available attribution types. Can be null if the deposit is not
            attributed.
          enum:
            - MANUAL_STAFF
            - MANUAL_CLIENT
            - CLIENT_API
            - AUTOMATIC
            - SPAM
            - TRUSTED_SOURCES
          example: CLIENT_API
        sourceWalletType:
          type: string
          description: >-
            The type of wallet for the originator of the deposit. Can be null if
            the deposit is not attributed.
          enum:
            - CUSTODIAL
            - SELF_HOSTED
        originatorName:
          description: >-
            The name of the originator of the deposit. Can be null if the
            deposit is not attributed.
          type: string
          example: John Doe
        originatorCountry:
          description: >-
            The country of the originator of the deposit. Can be null if the
            deposit is not attributed.
          type: string
          example: US
        notes:
          description: >-
            Additional notes for the deposit attribution. Can be null if the
            deposit is not attributed.
          type: string
        accountId:
          description: >-
            The Account Identifier for the account associated with the deposit.
            Can be null if there is no account associated with this use case.
          type: string
          format: uuid
          example: 3486b413-93d3-4447-afce-2b9c9dc34a32
        blockchainTxId:
          description: >-
            Blockchain transaction id of the deposit associated to the
            attribution.
          type: string
          example: '0x84ddb76708d570101db89fd27b1717484c54417c9f32c63052cdfac9a0bfc0a2'
        assetType:
          description: >
            A string representing a type of crypto-asset, which usually
            corresponds to the crypto asset's ticker symbol.


            Use `/asset-types` to list all of the supported asset types for your
            organization.
          type: string
          example: ETH
      required:
        - depositTransactionId
        - status
        - sourceAddresses
        - createdAt
        - blockchainTxId
        - assetType
    Page:
      title: Page
      description: Pagination info
      type: object
      properties:
        endCursor:
          description: Submit this parameter in the "after" field to fetch the next page.
          type: string
          nullable: true
    ErrorDetails:
      title: ErrorDetails
      type: object
      properties:
        message:
          description: A human-readable message providing more details about the error.
          example: Missing required field 'amount'.
          type: string
      required:
        - message
  securitySchemes:
    Api-Access-Key:
      type: apiKey
      name: Api-Access-Key
      in: header
      description: An API key associated with a security role

````

## Related topics

- [List deposit attributions](https://docs.anchorage.com/knowledge-base/porto/api-reference/v2/deposit-attribution/list-deposit-attributions.md)
- [Deposit](https://docs.anchorage.com/knowledge-base/platform/developers/move-money/deposit.md)
- [Crypto deposits](https://docs.anchorage.com/knowledge-base/platform/developers/caas/caas-deposits-crypto.md)
- [Track movement status](https://docs.anchorage.com/knowledge-base/platform/developers/move-money/operate/track-status.md)
