> ## 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 customer documents

> Permissions required: **Read Customers**

List the documents associated with a customer. Document upload URLs (when
present) are short-lived; always refresh via this endpoint before uploading.



## OpenAPI

````yaml /knowledge-base/openapi/v4.yaml get /customers/{customerId}/documents
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:
  /customers/{customerId}/documents:
    get:
      tags:
        - Customers
      summary: List customer documents
      description: >-
        Permissions required: **Read Customers**


        List the documents associated with a customer. Document upload URLs
        (when

        present) are short-lived; always refresh via this endpoint before
        uploading.
      operationId: listCustomerDocuments
      parameters:
        - name: customerId
          in: path
          schema:
            type: string
            format: uuid
            example: 3486b413-93d3-4447-afce-2b9c9dc34a32
          required: true
          description: Unique identifier for the customer
        - 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
      responses:
        '200':
          description: List of documents
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ListCustomerDocumentsResponse'
        '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'
        '404':
          description: Not Found
          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:
    ListCustomerDocumentsResponse:
      title: List Customer Documents Response
      type: object
      required:
        - data
        - page
      properties:
        data:
          type: array
          items:
            $ref: '#/components/schemas/OnboardingDocument'
        page:
          $ref: '#/components/schemas/Page'
    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
    OnboardingDocument:
      title: Onboarding Document
      type: object
      description: A document associated with a customer
      required:
        - documentId
        - state
      properties:
        documentId:
          type: string
          description: Unique identifier for the document
        state:
          $ref: '#/components/schemas/OnboardingDocumentState'
        signedUrl:
          type: string
          description: Signed URL for accessing the document
          nullable: true
        expiresAt:
          description: Expiration time of the signed URL
          nullable: true
          type: string
          format: date-time
          example: '2019-01-02T12:34:56.000Z'
    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
    OnboardingDocumentState:
      title: Onboarding Document State
      type: string
      description: The state of a document
      enum:
        - PENDING
        - UPLOADED
        - VERIFIED
        - REJECTED
  securitySchemes:
    Api-Access-Key:
      type: apiKey
      name: Api-Access-Key
      in: header
      description: An API key associated with a security role

````

## Related topics

- [List customers](https://docs.anchorage.com/knowledge-base/api-reference/v4/customers/list-customers.md)
- [List customer onboarding applications](https://docs.anchorage.com/knowledge-base/api-reference/v2-platforms/onboarding/list-customer-onboarding-applications.md)
- [Get customer](https://docs.anchorage.com/knowledge-base/api-reference/v4/customers/get-customer.md)
- [Update customer](https://docs.anchorage.com/knowledge-base/api-reference/v4/customers/update-customer.md)
- [Create customers](https://docs.anchorage.com/knowledge-base/api-reference/v4/customers/create-customers.md)
