> ## Documentation Index > Fetch the complete documentation index at: https://docs.hifi.com/llms.txt > Use this file to discover all available pages before exploring further. # Create a user > Create a new Hifi user. ## OpenAPI ````yaml https://production.hifi.com/api/v3/openapi.json post /v3/users openapi: 3.0.0 info: title: Hifi API version: 3.0.0 description: API documentation for HIFI servers: - url: https://production.hifi.com description: Production server - url: https://sandbox.hifi.com description: Sandbox server security: - bearerAuth: [] tags: - name: Common description: Common endpoints - name: User description: User endpoints - name: Counter Party description: Counter party endpoints - name: Crypto Transfer description: Crypto transfer and batch transfer endpoints - name: Wallet description: Wallet and wallet offer endpoints - name: External Account description: External bank account endpoints (under a counter party) - name: External Wallet description: External wallet endpoints (under a counter party) - name: External Card description: External card endpoints (under a counter party) - name: Token Swap description: Token swap endpoints - name: Bridge description: Bridge endpoints - name: Virtual Account description: Virtual account endpoints - name: Compliance description: Compliance and compliance link endpoints - name: Webhook Endpoint description: Webhook endpoint endpoints - name: File description: File upload endpoints - name: Onramp description: Onramp (fiat to crypto) endpoints - name: Offramp description: Offramp (crypto to fiat) endpoints - name: Orchestration Address description: Orchestration (liquidation) address endpoints - name: KYC Link description: Hosted and custom KYC/KYB link endpoints - name: Transfer Approval description: Transfer approval endpoints - name: Corridor description: Supported fiat/crypto transfer corridor endpoints - name: Migration description: v2-to-v3 ID mapping endpoints paths: /v3/users: post: tags: - User summary: Create a user description: Create a new Hifi user. operationId: v3CreateUser requestBody: $ref: '#/components/requestBodies/UserCreateBody' responses: '201': $ref: '#/components/responses/UserObjectResponse' '401': $ref: '#/components/responses/UnauthorizedResponse' '404': $ref: '#/components/responses/NotFoundResponse' '409': $ref: '#/components/responses/ConflictResponse' '500': $ref: '#/components/responses/InternalServerErrorResponse' components: requestBodies: UserCreateBody: required: true content: application/json: schema: $ref: '#/components/schemas/UserCreate' responses: UserObjectResponse: description: Success content: application/json: schema: $ref: '#/components/schemas/UserObject' examples: IndividualUserObjectExample: $ref: '#/components/examples/IndividualUserObjectExample' BusinessUserObjectExample: $ref: '#/components/examples/BusinessUserObjectExample' UnauthorizedResponse: description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/Unauthorized' NotFoundResponse: description: Not Found content: application/json: schema: $ref: '#/components/schemas/NotFound' ConflictResponse: description: >- Conflict — the request collides with the current state of the resource (e.g. idempotency-key reuse with a different payload). content: application/json: schema: $ref: '#/components/schemas/ApiError' example: type: RESOURCE_CONFLICT message: Resource already exists or conflicts with current state InternalServerErrorResponse: description: Internal Server Error content: application/json: schema: $ref: '#/components/schemas/InternalServerError' schemas: UserCreate: type: object properties: requestId: type: string description: Optional idempotency key for user creation. type: type: string enum: - individual - business signedAgreementId: type: string format: uuid description: ID of the signed agreement from POST /v3/tos-link. required: - type - signedAgreementId UserObject: type: object properties: id: type: string pattern: ^user_[A-Za-z0-9]+$ description: User ID. type: type: string enum: - INDIVIDUAL - BUSINESS createdAt: type: string format: date-time description: Timestamp when the user was created. updatedAt: type: string format: date-time description: Timestamp when the user was last updated. required: - id - type - createdAt - updatedAt Unauthorized: type: object properties: type: type: string description: Unauthorized enum example: UNAUTHORIZED message: type: string description: Unauthorized message example: Authentication required NotFound: type: object properties: type: type: string example: RESOURCE_NOT_FOUND description: The error type, e.g., RESOURCE_NOT_FOUND message: type: string description: A descriptive error message fields: type: array description: List of specific field errors items: type: object properties: code: type: string description: Error code related to the field issue message: type: string description: Error message for the specific issue field: type: string description: The name of the field that has an issue ApiError: type: object description: >- Standard v3 error shape, returned by validation failures and business-logic errors alike. properties: type: type: string description: >- Machine-readable error type, e.g. VALIDATION_ERROR, ACTION_NOT_ALLOWED, RESOURCE_CONFLICT. example: VALIDATION_ERROR message: type: string description: Human-readable error message. example: One or more fields are invalid or missing. fields: type: array description: >- Present on field-level validation errors. One entry per problem field. items: type: object properties: code: type: string description: Error code related to the field issue. message: type: string description: Error message for the specific issue. field: type: string description: The name of the field that has an issue. InternalServerError: type: object properties: type: type: string example: INTERNAL_SERVER_ERROR description: Internal server error enum message: type: string example: An internal server error occurred description: Internal server error message examples: IndividualUserObjectExample: summary: Individual User Object value: id: user_2f7a9bc3d4e5 type: INDIVIDUAL createdAt: '2026-07-09T16:12:20.541Z' updatedAt: '2026-07-09T16:12:20.541Z' BusinessUserObjectExample: summary: Business User Object value: id: user_9a8b7c6d5e4f type: BUSINESS createdAt: '2026-07-09T16:03:41.107Z' updatedAt: '2026-07-09T16:03:41.107Z' securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT ````