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

# Create a new wallet asset for a customer

> Provisions a crypto wallet for a customer for the requested asset and
chain, returning the created wallet. Pass an Idempotency-Key header to
safely retry without provisioning duplicates.



## OpenAPI

````yaml /api-reference/openapi.yaml post /customers/{id}/wallets
openapi: 3.0.3
info:
  title: Polygon OMS Public API
  version: v26.05.28-0001
  description: >-
    Unified API for moving money between crypto and fiat. Three ways to move
    money: Transactions (instant, wallet or card funded, including Cash-In for
    in-person cash deposits), Deposit Addresses (reusable crypto deposit
    configurations), and Virtual Accounts (dedicated bank accounts that
    auto-convert fiat to crypto). Standard transactions follow a two-step flow:
    create a Quote (pricing), then create a Transaction (execution). Cash-in
    codes generate a one-time deposit code for in-person cash deposits at retail
    locations.
  contact:
    name: Polygon OMS
    url: https://oms.polygon.technology
servers:
  - url: https://sandbox-api.polygon.technology/v0.10
    description: Sandbox
  - url: https://api.polygon.technology/v0.10
    description: Production
security:
  - BearerAuth: []
tags:
  - name: Auth
    description: Authentication via FrontEgg
  - name: Customers
    description: Customer management and KYC
  - name: Customer
  - name: Wallet
  - name: Quote
  - name: Transaction
  - name: Webhook
  - name: CashIns
  - name: CashLocation
  - name: Sandbox
  - name: VirtualAccount
  - name: Counterparty
  - name: ExternalAccount
  - name: DepositAddress
  - name: Simulation
paths:
  /customers/{id}/wallets:
    post:
      tags:
        - Wallet
      summary: Create a new wallet asset for a customer
      description: |-
        Provisions a crypto wallet for a customer for the requested asset and
        chain, returning the created wallet. Pass an Idempotency-Key header to
        safely retry without provisioning duplicates.
      operationId: createCustomerWallet
      parameters:
        - in: path
          name: id
          required: true
          schema:
            type: string
        - $ref: '#/components/parameters/IdempotencyKeyHeader'
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/WalletCreateRequest'
        required: true
      responses:
        '201':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Wallet'
          description: >-
            The request has succeeded and a new resource has been created as a
            result.
components:
  parameters:
    IdempotencyKeyHeader:
      description: >-
        Required on POST and PUT requests. Use a unique value per logical
        mutation attempt, for example a UUID.
      in: header
      name: Idempotency-Key
      required: true
      schema:
        type: string
  schemas:
    WalletCreateRequest:
      description: >-
        Request body for creating a wallet: the asset to hold and the chain it
        lives on.
      properties:
        asset:
          type: string
        chain:
          type: string
      required:
        - asset
        - chain
      type: object
    Wallet:
      description: >-
        A wallet holding a single asset on one chain for a customer. internal
        wallets are OMS-managed; external wallets are held outside OMS.
      properties:
        address:
          type: string
        asset:
          type: string
        blockchainAsset:
          $ref: '#/components/schemas/BlockchainAsset'
        chain:
          type: string
        createdAt:
          type: string
          format: date-time
        customerId:
          type: string
        id:
          type: string
        object:
          enum:
            - wallet
          type: string
        status:
          $ref: '#/components/schemas/WalletStatus'
        type:
          $ref: '#/components/schemas/WalletType'
        updatedAt:
          type: string
          format: date-time
      type: object
    BlockchainAsset:
      description: >-
        On-chain identity for an asset: the chain it lives on, the wire-level
        protocol (EVM, SVM, Sui), and the token identifier within that chain.
      properties:
        chainId:
          description: >-
            Chain identifier within the protocol (for example, an EVM chain ID
            or a Solana cluster name).
          type: string
        protocol:
          $ref: '#/components/schemas/BlockchainProtocol'
        tokenId:
          description: >-
            Token identifier on the chain (for example, an ERC-20 contract
            address or an SPL mint address). Use the chain's canonical
            representation for the native asset.
          type: string
      required:
        - protocol
        - chainId
        - tokenId
      type: object
    WalletStatus:
      enum:
        - active
        - suspended
        - closed
      type: string
    WalletType:
      description: >-
        Whether a wallet is internal (OMS-managed) or external (held outside
        OMS).
      enum:
        - internal
        - external
      type: string
    BlockchainProtocol:
      description: >-
        Wire-level protocol family for a chain. `evm` covers Ethereum-compatible
        chains, `svm` covers the Solana virtual machine, and `sui` covers the
        Sui Move VM.
      enum:
        - evm
        - svm
        - sui
      type: string
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: Token from POST /auth/token

````