> ## Documentation Index > Fetch the complete documentation index at: https://docs.iron.xyz/llms.txt > Use this file to discover all available pages before exploring further. # Create a new Customer signing > This will create a signing for the customer, representing the legal consent to a specific Document. See The KYC/Compliance section of our documentation for more info. ## OpenAPI ````yaml /spec.yaml post /customers/{id}/signings openapi: 3.1.0 info: description: The Stablecoin Payment Network title: Iron API - Sandbox version: 1.0-16884 servers: - url: https://api.sandbox.iron.xyz/api security: [] tags: - description: >- Wallet and bank account registration Every wallet address that interacts with Iron must be registered (linked) to a customer **before** it can be used in any flow — onramp, offramp, or swap. This is a regulatory requirement under the **Travel Rule**, which obliges Virtual Asset Service Providers to exchange originator and beneficiary information for crypto transfers. Iron supports two wallet types: - **Self-hosted wallets** — the customer controls the private key. Registration requires a signed proof-of-ownership message. - **Hosted wallets** — the wallet is custodied by another VASP (e.g. Coinbase, Kraken). Registration requires the VASP's DID so Iron can exchange travel-rule data with the custodian. Similarly, fiat bank accounts must be registered before they can receive offramp payouts. name: Addresses - description: Operations on Autoramp name: Autoramp - description: Operations on Chronicle collateral name: ChronicleCollateral - description: Operations on Currencies name: Currencies - description: Operations on Customers name: Customer - description: Operations on Exchange Rate name: ExchangeRate - description: Operations on Fee Profiles name: FeeProfiles - description: Operations for Sandbox Testing name: Sandbox - description: Operations on SSE name: Sse - description: Operations on Terms and Conditions name: TermsAndConditions - description: Operations on Webhooks name: Webhooks paths: /customers/{id}/signings: post: tags: - Customer summary: Create a new Customer signing description: >+ This will create a signing for the customer, representing the legal consent to a specific Document. See The KYC/Compliance section of our documentation for more info. operationId: createCustomerSigning parameters: - deprecated: false description: a UUID ensuring an Signing operation is only processed once explode: true in: header name: IDEMPOTENCY-KEY required: true schema: type: string - deprecated: false description: >- Optional sub-partner UUID, if provided, the signing will be created under scope of the sub-partner explode: true in: header name: X-SUB-PARTNER-ID required: false schema: type: string - deprecated: false description: the ID of the Customer to create a Signing for explode: true in: path name: id required: true schema: format: uuid type: string - $ref: '#/components/parameters/XApiVersion' requestBody: content: application/json; charset=utf-8: schema: $ref: '#/components/schemas/SigningCreateParams' description: Parameters required to create a new Signing required: true responses: '201': content: application/json; charset=utf-8: schema: $ref: '#/components/schemas/Signing' description: POST Signing Succeeded '401': content: application/json; charset=utf-8: schema: type: string description: POST Signing Failed (Unauthorized) '403': content: application/json; charset=utf-8: schema: type: string description: POST Signing Failed (Forbidden) '404': content: application/json; charset=utf-8: schema: type: string description: POST Signing Failed (Not Found) '422': content: application/json; charset=utf-8: schema: type: string description: POST Signing Failed (Validation Error) '500': content: application/json; charset=utf-8: schema: $ref: '#/components/schemas/ApiError' description: POST Signing Failed (Internal Error) security: - ApiKeyAuth: [] components: parameters: XApiVersion: description: >- Selects the API version for this request, as an ISO date (`YYYY-MM-DD`). Omit to use the default version (`2025-03-13`). Supported versions: 2025-03-13, 2026-07-01. in: header name: X-API-Version required: false schema: type: string schemas: SigningCreateParams: description: Params for Creating a Signing example: content_id: 019f700d-17ac-75e3-bbeb-26929b6057f3 signed: true properties: content_id: description: unique UUID of the content signed by Customer format: uuid type: string signed: description: Explicit signing consent type: boolean required: - signed title: SigningCreateParams type: object Signing: description: | Signing A signing of a document by a customer properties: content_id: description: unique UUID of the content signed by Customer format: uuid type: string created_at: description: created_at timestamp of Signing format: date-time type: string customer_id: description: unique UUID of the Customer who signed format: uuid type: string document_id: description: >- unique UUID of the Document signed by Customer (Soon to be deprecated, use content_id & content_type instead) format: uuid type: string id: description: unique UUID of Signing format: uuid type: string updated_at: description: updated_at timestamp of Signing format: date-time type: string required: - id - customer_id - created_at - updated_at title: Signing type: object ApiError: description: |- Standard error response returned to API clients for server errors. Includes a trace_id that clients can reference when reporting issues. properties: message: description: Human-readable error message type: string trace_id: description: Trace ID that can be used to look up request details in logs type: string required: - message - trace_id title: ApiError type: object securitySchemes: ApiKeyAuth: description: API Key in: header name: X-API-Key type: apiKey ````