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

# Create User

> Create a new organization user.



## OpenAPI

````yaml post /v1/organizations/users
openapi: 3.1.0
info:
  title: Mixpeek API
  description: >-
    This is the Mixpeek API, providing access to various endpoints for data
    processing and retrieval.
  termsOfService: https://mixpeek.com/terms
  contact:
    name: Mixpeek Support
    url: https://mixpeek.com/contact
    email: info@mixpeek.com
  version: '0.82'
servers:
  - url: https://api.mixpeek.com
    description: Production
security: []
paths:
  /v1/organizations/users:
    post:
      tags:
        - Organization Users
      summary: Create User
      description: Create a new organization user.
      operationId: create_user_v1_organizations_users_post
      parameters: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/UserCreateRequest'
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
                title: Response Create User V1 Organizations Users Post
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '403':
          description: Forbidden
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '404':
          description: Not Found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
components:
  schemas:
    UserCreateRequest:
      properties:
        email:
          type: string
          format: email
          title: Email
          description: Unique email address within the organization.
        user_name:
          type: string
          maxLength: 100
          minLength: 2
          title: User Name
          description: Display name shown in dashboards and audit trails.
        avatar_url:
          anyOf:
            - type: string
            - type: 'null'
          title: Avatar Url
          description: Profile picture URL (e.g., from PropelAuth picture_url property).
        role:
          $ref: '#/components/schemas/UserRole'
          description: Default role within the organization if omitted.
          default: member
        status:
          $ref: '#/components/schemas/UserStatus'
          description: >-
            Initial lifecycle status. Use 'pending' for invited users who
            haven't accepted yet.
          default: active
        metadata:
          anyOf:
            - additionalProperties: true
              type: object
            - type: 'null'
          title: Metadata
          description: Custom key/value metadata stored with the user record.
      type: object
      required:
        - email
        - user_name
      title: UserCreateRequest
      description: Payload for creating an organization user.
      examples:
        - email: alice@example.com
          role: member
          user_name: Alice Smith
        - email: bob@example.com
          metadata:
            department: Engineering
          role: admin
          user_name: Bob Johnson
    ErrorResponse:
      properties:
        success:
          type: boolean
          title: Success
          description: Always false for error responses
          default: false
        status:
          type: integer
          title: Status
          description: HTTP status code for this error
        error:
          $ref: '#/components/schemas/ErrorDetail'
          description: Error details payload
      type: object
      required:
        - status
        - error
      title: ErrorResponse
      description: Error response model.
      examples:
        - error:
            details:
              id: ns_123
              resource: namespace
            message: Namespace not found
            type: NotFoundError
          status: 404
          success: false
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    UserRole:
      type: string
      enum:
        - admin
        - member
        - viewer
      title: UserRole
      description: >-
        High-level organization role applied to users.


        Roles define the baseline permissions a user has within an organization:


        - ADMIN: Full administrative access including user management, billing,
          and organization settings. Can create/modify/delete all resources.
        - MEMBER: Standard user access. Can create and manage their own
        resources
          (namespaces, collections, clusters) but cannot manage other users or
          organization-level settings.
        - VIEWER: Read-only access. Can view resources and execute retrievers
        but
          cannot create, modify, or delete any resources.
    UserStatus:
      type: string
      enum:
        - active
        - suspended
        - pending
      title: UserStatus
      description: >-
        Lifecycle state of an organization user.


        Status values control whether a user can authenticate and access
        resources:


        - ACTIVE: User is fully operational and can authenticate with their API
        keys.

        - SUSPENDED: User access is temporarily disabled. API keys will not work
        but
          account data is preserved. Can be reactivated by an admin.
        - PENDING: User invitation has been created but not yet accepted. User
        cannot
          authenticate until they complete the onboarding flow.
    ErrorDetail:
      properties:
        message:
          type: string
          title: Message
          description: Human-readable error message
        type:
          type: string
          title: Type
          description: Stable error type identifier (machine-readable)
        code:
          anyOf:
            - type: string
            - type: 'null'
          title: Code
          description: >-
            Fine-grained error code for programmatic handling (e.g.,
            namespace_name_taken, feature_extractor_not_found). Present only
            when consumers may need to branch on a specific error condition.
        details:
          anyOf:
            - additionalProperties: true
              type: object
            - type: 'null'
          title: Details
          description: >-
            Optional structured details to help debugging (validation errors,
            IDs, etc.)
      type: object
      required:
        - message
        - type
      title: ErrorDetail
      description: Error detail model.
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError

````