> ## Documentation Index > Fetch the complete documentation index at: https://developers.circle.com/llms.txt > Use this file to discover all available pages before exploring further. # Create a partner client > Creates a new client entity and initializes an onboarding application in a single request. The response contains both the `clientEntityId` and the `applicationId` for the newly created draft application. A unique combination of `clientName` and `country` is required. Submitting a duplicate combination returns a `409 Conflict` error. ## OpenAPI ````yaml openapi/customer-orchestration.yaml post /v1/partner/clients openapi: 3.0.2 info: version: ${version} title: Customer Orchestration API description: > API for managing partner client entities. Use these endpoints to create a client record and initialize an onboarding application on behalf of your customer, and to read back the clients created under your partner account. ## Authentication All endpoints require a Bearer token obtained via the Circle key exchange. Include the token in the `Authorization: Bearer ` header. servers: - url: https://api-sandbox.circle.com - url: https://api.circle.com security: [] tags: - name: Partner Clients description: >- Create client entities, initialize onboarding applications, and read back the clients created under your partner account. paths: /v1/partner/clients: post: tags: - Partner Clients summary: Create a partner client description: >- Creates a new client entity and initializes an onboarding application in a single request. The response contains both the `clientEntityId` and the `applicationId` for the newly created draft application. A unique combination of `clientName` and `country` is required. Submitting a duplicate combination returns a `409 Conflict` error. operationId: createPartnerClient requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/CreatePartnerClientRequest' responses: '200': description: Client created and application initialized headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: $ref: '#/components/schemas/CreatePartnerClientResponse' '401': $ref: '#/components/responses/NotAuthorized' '403': $ref: '#/components/responses/Forbidden' '409': $ref: '#/components/responses/Conflict' security: - bearerAuth: [] components: schemas: CreatePartnerClientRequest: type: object required: - businessDetails - clientName - clientType - country properties: clientName: type: string description: Name for the client entity. example: Acme Trust Co. country: type: string description: >- ISO 3166-1 alpha-2 country code for the client's primary jurisdiction. example: US minLength: 2 maxLength: 2 clientType: type: string description: Type of client. Currently `business` is the only supported value. enum: - business example: business businessDetails: $ref: '#/components/schemas/BusinessDetails' CreatePartnerClientResponse: type: object properties: data: type: object properties: clientEntityId: type: string format: uuid description: Unique identifier for the newly created client entity. example: 880e8400-e29b-41d4-a716-446655440099 applicationId: type: string format: uuid description: >- Unique identifier for the draft onboarding application created for this client. example: 550e8400-e29b-41d4-a716-446655440000 BusinessDetails: type: object description: >- Business-specific details. On create, required only when `clientType` is `business` — omit this object for non-business client types. On reads, returned for business clients with the values submitted at creation. required: - institutionType - natureOfBusiness properties: natureOfBusiness: type: string description: >- Industry classification for the business. Determines which sections and fields appear in the onboarding application. enum: - accommodation - accounting - agriculture - art - assetManager - banking - brokerageOTC - construction - cryptoATM - cryptoCustodian - cryptoExchange - cryptoInvesting - cryptoSoftwareProvider - daOrg - dexAdmin - eCommercePlatform - education - familyOffice - film - healthCare - hedgeFund - insurance - manufacturingAutomobiles - manufacturingElectronics - manufacturingHighValueGoods - manufacturingOther - marketMaker - marketing - mining - miningPool - nftMarketplace - nonProfit - otherCryptoServices - otherOperatingCompanies - otherPooledInvestmentVehicles - p2p - paymentProcessorPlatform - personalInvestment - privateEquityFund - privateFoundation - publicCharity - realEstate - stakingServices - tokenProject - trading - transportation - trust - utilities - ventureCapitalFund - web3GamingSocial example: paymentProcessorPlatform institutionType: type: string description: Legal entity type of the business. enum: - associationOrConsortium - coop - foundation - governmentBody - partnership - privateCo - publicCo - soleTrader - trust example: privateCo headers: XRequestId: description: >- Universally unique identifier (UUID v4) for the request. Helpful for identifying a request when communicating with Circle support. schema: type: string format: uuid example: 2adba88e-9d63-44bc-b975-9b6ae3440dde responses: NotAuthorized: description: >- The request has not been applied because it lacks valid authentication credentials. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: type: object title: NotAuthorized required: - code - message properties: code: type: integer example: 401 message: type: string example: Malformed authorization. Forbidden: description: >- The request provides authentication, but the authenticated user does not possess sufficient permissions for accessing this resource. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: type: object title: Forbidden required: - code - message properties: code: type: integer example: 403 message: type: string example: Forbidden Conflict: description: >- A client with the same `clientName` and `country` combination already exists. Use a different `clientName` to create another client in the same country. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: type: object title: Conflict required: - code - message properties: code: type: integer example: 409 message: type: string example: A client with this name and country already exists. securitySchemes: bearerAuth: type: http scheme: bearer ````