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

# Create customers

> Permissions required: **Manage Customers**

Open one or more customer onboarding applications. Use
`GET /customers/{customerId}` to retrieve full details, including
documents, once creation completes.



## OpenAPI

````yaml /knowledge-base/openapi/v4.yaml post /customers
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:
    post:
      tags:
        - Customers
      summary: Create customers
      description: |-
        Permissions required: **Manage Customers**

        Open one or more customer onboarding applications. Use
        `GET /customers/{customerId}` to retrieve full details, including
        documents, once creation completes.
      operationId: createCustomers
      parameters:
        - name: Idempotency-Key
          in: header
          schema:
            type: string
          required: true
          description: >-
            Client-supplied key that deduplicates retried requests. Reusing a
            key returns the original result instead of repeating the action.
        - name: Api-Signature
          in: header
          required: true
          schema:
            type: string
            pattern: ^[0-9A-Fa-f]{128,160}$
          description: >-
            A hex-encoded Ed25519 signature of `timestamp_epoch_seconds +
            uppercase(http_method) + request_path + request_body`.
        - name: Api-Timestamp
          in: header
          required: true
          schema:
            type: integer
            format: int64
          description: Current timestamp, represented as unix epoch seconds
      requestBody:
        description: Customers to create
        required: true
        content:
          application/json:
            schema:
              type: array
              items:
                $ref: '#/components/schemas/CreateCustomerRequest'
      responses:
        '202':
          description: Accepted
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CreateCustomersResponse'
        '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'
        '409':
          description: Conflict
          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:
    CreateCustomerRequest:
      title: Create Customer Request
      description: Request to create a new customer. Discriminated on customerType.
      discriminator:
        propertyName: customerType
        mapping:
          INDIVIDUAL: '#/components/schemas/CreateIndividualCustomerRequest'
          BUSINESS: '#/components/schemas/CreateBusinessCustomerRequest'
      oneOf:
        - $ref: '#/components/schemas/CreateIndividualCustomerRequest'
        - $ref: '#/components/schemas/CreateBusinessCustomerRequest'
    CreateCustomersResponse:
      title: Create Customers Response
      description: Per-item results for a batch customer creation request.
      type: object
      required:
        - data
      properties:
        data:
          type: array
          items:
            $ref: '#/components/schemas/BatchItemResult'
    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
    CreateIndividualCustomerRequest:
      title: Create Individual Customer
      type: object
      description: Request to create a new individual customer
      properties:
        customerType:
          type: string
          enum:
            - INDIVIDUAL
          default: INDIVIDUAL
          description: Discriminator — always INDIVIDUAL
        externalId:
          type: string
          description: External identifier provided by the client
        firstName:
          type: string
          description: First name of the individual
        lastName:
          type: string
          description: Last name of the individual
        dateOfBirth:
          type: string
          format: date
          description: Date of birth
        email:
          type: string
          format: email
          description: Email address
        idNumber:
          type: string
          description: Government-issued identification number
        address:
          $ref: '#/components/schemas/CustomerAddress'
      required:
        - customerType
        - externalId
        - firstName
        - lastName
        - email
        - idNumber
        - address
      additionalProperties: false
    CreateBusinessCustomerRequest:
      title: Create Business Customer
      type: object
      description: Request to create a new business customer
      properties:
        customerType:
          type: string
          enum:
            - BUSINESS
          default: BUSINESS
          description: Discriminator — always BUSINESS
        externalId:
          type: string
          description: External identifier provided by the client
        legalName:
          type: string
          description: Legal name of the business
        dbaNames:
          type: string
          description: Doing business as names
        registrationNumber:
          type: string
          description: Business registration number
        legalStructure:
          type: string
          description: Legal structure of the business
          enum:
            - C_CORP
            - LLC
            - LLP
            - LP
            - S_CORP
            - SOLE_PROP
            - TRUST
            - NON_PROFIT
            - OTHER
        dateOfIncorporation:
          type: string
          format: date
          description: Date of incorporation
        address:
          $ref: '#/components/schemas/CustomerAddress'
      required:
        - customerType
        - externalId
        - legalName
        - registrationNumber
        - address
      additionalProperties: false
    BatchItemResult:
      title: Batch Item Result
      type: object
      description: The per-item result of a batch action, discriminated by status.
      discriminator:
        propertyName: status
        mapping:
          SUCCESS: '#/components/schemas/BatchItemSuccessResult'
          ERROR: '#/components/schemas/BatchItemErrorResult'
      oneOf:
        - $ref: '#/components/schemas/BatchItemSuccessResult'
        - $ref: '#/components/schemas/BatchItemErrorResult'
    CustomerAddress:
      title: Customer Address
      type: object
      description: A structured postal address
      required:
        - country
      properties:
        country:
          type: string
          description: Country
        streetAddress:
          type: string
          description: Street address
          nullable: true
        city:
          type: string
          description: City
          nullable: true
        state:
          type: string
          description: State or province
          nullable: true
        postalCode:
          type: string
          description: Zip code or postal code
          nullable: true
    BatchItemSuccessResult:
      title: Batch Item Success Result
      type: object
      description: Successful outcome for one item of a batch request.
      properties:
        index:
          $ref: '#/components/schemas/BatchItemIndex'
        id:
          $ref: '#/components/schemas/BatchItemId'
        status:
          type: string
          description: Outcome of the action for this item
          enum:
            - SUCCESS
          default: SUCCESS
      required:
        - index
        - id
        - status
    BatchItemErrorResult:
      title: Batch Item Error Result
      type: object
      description: >-
        Failed outcome for one item of a batch request. Other items in the same
        batch may still have succeeded.
      properties:
        index:
          $ref: '#/components/schemas/BatchItemIndex'
        id:
          $ref: '#/components/schemas/BatchItemId'
        status:
          type: string
          description: Outcome of the action for this item
          enum:
            - ERROR
          default: ERROR
        error:
          description: Human-readable reason the item failed.
          type: string
      required:
        - index
        - status
        - error
    BatchItemIndex:
      title: Batch Item Index
      type: integer
      minimum: 0
      description: >-
        The 0-based position of this item in the request. Always present
        regardless of outcome, so a result can be correlated with its request
        item even when no id was ever assigned.
    BatchItemId:
      title: Batch Item ID
      type: string
      description: >-
        Unique identifier of the item this result applies to. Always present on
        success. On error, present only if an id was assigned before the item
        failed (e.g. an existing entity targeted by an action); absent when the
        item was rejected before any id could exist, such as a failed validation
        on creation. Use `index` to correlate a result with its request item
        when `id` is absent.
  securitySchemes:
    Api-Access-Key:
      type: apiKey
      name: Api-Access-Key
      in: header
      description: An API key associated with a security role

````

## Related topics

- [Create customers](https://docs.anchorage.com/knowledge-base/platform/developers/named-virtual-accounts/named-virtual-accounts-create-customers.md)
- [Create virtual accounts](https://docs.anchorage.com/knowledge-base/platform/developers/named-virtual-accounts/named-virtual-accounts-create-virtual-accounts.md)
- [Overview](https://docs.anchorage.com/knowledge-base/platform/developers/named-virtual-accounts/named-virtual-accounts-overview.md)
- [Create a new subaccount for a given program customer](https://docs.anchorage.com/knowledge-base/porto/api-reference/v2/subaccounts/create-a-new-subaccount-for-a-given-program-customer.md)
- [Create a virtual account for a wallet](https://docs.anchorage.com/knowledge-base/api-reference/v2-platforms/virtual-accounts/create-a-virtual-account-for-a-wallet.md)
