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

# Create Customer

> Creates a new customer account (individual or business). This is the foundational step for other API use cases.



## OpenAPI

````yaml ramps-api/openapi.json POST /api/v1/customers/
openapi: 3.1.0
info:
  title: Ripio Ramp API
  version: v1
  description: >-
    API for Ripio ramp services, enabling partners to integrate On-Ramp,
    Off-Ramp, customer management, KYC processes, and other financial
    functionalities. This API is RESTful, uses JSON for requests and responses,
    and standard HTTP status codes. This document is based on the
    'onramp-api.pdf' provided and aims to be compliant with OpenAPI
    Specification v3.1.0. The PDF indicates that the API documentation is a
    draft and subject to change.
servers:
  - url: https://skala-sandbox.ripio.com
    description: Sandbox environment
  - url: https://skala.ripio.com
    description: Production environment
security:
  - BearerToken: []
tags:
  - name: Authentication
    description: Operations related to API authentication and authorization.
  - name: Customers
    description: Operations related to customer management.
  - name: KYC
    description: Operations related to Know Your Customer processes.
  - name: Fiat Accounts
    description: Operations related to managing fiat accounts and their requirements.
  - name: Quotes
    description: Operations related to obtaining and managing conversion quotes.
  - name: On-Ramp
    description: Operations related to fiat-to-crypto (on-ramp) processes.
  - name: Off-Ramp
    description: Operations related to crypto-to-fiat (off-ramp) processes.
  - name: Transactions
    description: Operations related to listing and managing all transaction types.
  - name: Networks
    description: >-
      Operations related to retrieving available deposit and withdrawal
      networks.
  - name: Rates
    description: Operations related to retrieving market rates.
  - name: Sandbox
    description: Operations specific to the sandbox environment for testing purposes.
  - name: Webhooks
    description: Webhook event notifications from Ripio Ramp API.
  - name: Sell and Pay
    description: >-
      Endpoints for managing Sell and Pay transactions, which allow customers to
      convert cryptocurrency to fiat currency and pay merchants via QR codes
paths:
  /api/v1/customers/:
    post:
      tags:
        - Customers
      summary: Create Customer
      description: >-
        Creates a new customer account (individual or business). This is the
        foundational step for other API use cases.
      operationId: createCustomer
      requestBody:
        required: true
        description: Customer creation payload.
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CustomerCreationRequest'
      responses:
        '201':
          description: Customer created successfully.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CustomerResponse'
        '400':
          description: >-
            Bad Request - e.g., invalid input data, missing required fields, or
            customerId already exists.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          description: Unauthorized - Invalid or missing access token.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                code: 40001
                type: NotAuthenticated
                detail:
                  message: Authentication credentials were not provided.
                  code: not_authenticated
                status: 401
components:
  schemas:
    CustomerCreationRequest:
      type: object
      description: Payload for creating a new customer.
      properties:
        email:
          type: string
          format: email
          description: The email of the individual or juridical person.
          example: individual@mail.com
        type:
          type: string
          description: The type of customer involved.
          enum:
            - INDIVIDUAL
            - BUSINESS
          example: INDIVIDUAL
      required:
        - customerId
        - email
        - type
    CustomerResponse:
      type: object
      description: Response payload for a customer.
      properties:
        customerId:
          type: string
          description: A unique customer's ID.
          example: 7142b065-79c4-4f48-9e33-11b23bg689e2
        email:
          type: string
          format: email
          description: The email of the individual or juridical person.
          example: individual@mail.com
        isActive:
          type: boolean
          description: >-
            Whether the customer account is active. Returns `false` after the
            customer has been deactivated; in that case, operations on the
            customer's resources (KYC, fiat accounts, transactions, sessions)
            return 404.
          example: true
        createdAt:
          type: string
          format: date-time
          description: The date and time of customer's creation.
          example: '2024-04-10T18:17:07.702533Z'
    ErrorResponse:
      type: object
      properties:
        code:
          type: integer
          description: Application-specific error code.
        type:
          type: string
          description: Type of error or exception.
        detail:
          type: object
          properties:
            message:
              type: string
              description: Detailed error message.
          additionalProperties: true
        status:
          type: integer
          description: HTTP status code.
      required:
        - code
        - type
        - detail
        - status
  securitySchemes:
    BearerToken:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >-
        Access token obtained via
        [/oauth2/token/](/ramps-api/authentication/acquire-access-token). Use as
        `Authorization: Bearer <access_token>`.

````