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

# Invite users to the organization

> Creates one or more organization invitations. Each email domain must be registered to the organization. If you provide a team ID, the team must belong to the caller's workspace. Requests with more than two email addresses are processed in the background.



## OpenAPI

````yaml /openapi/admin-users.json post /platform/v1/admin/invites
openapi: 3.0.3
info:
  title: Qodo API
  version: '2026-09-03'
  description: >-
    Use the User management API to list, invite, update, and remove members in
    your Qodo organization. The API is currently available for eligible
    single-tenant organizations. Qodo must enable API access for your
    organization before you can use these endpoints.


    Authenticate with a personal `sk-` API key that belongs to an organization
    owner. See [Set up the User management
    API](/account-management/user-management-api).


    The `/platform/v1` segment versions the API contract. It is independent of
    the Qodo 1.x and Qodo 2.x product documentation versions.
servers:
  - url: https://qodo-platform.{tenant}.st.qodo.ai
    description: Your Qodo single-tenant API host
    variables:
      tenant:
        default: your-tenant
        description: >-
          Replace this value with your Qodo tenant subdomain before sending a
          request.
security:
  - bearerAuth: []
tags:
  - name: API reference
    description: >-
      Manage registered users and pending invitations. Organization owner access
      is required.
paths:
  /platform/v1/admin/invites:
    post:
      tags:
        - API reference
      summary: Invite users to the organization
      description: >-
        Creates one or more organization invitations. Each email domain must be
        registered to the organization. If you provide a team ID, the team must
        belong to the caller's workspace. Requests with more than two email
        addresses are processed in the background.
      operationId: inviteUsersToOrganization
      parameters:
        - $ref: '#/components/parameters/RequestId'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/InviteUsersRequest'
            example:
              emails:
                - developer@example.com
                - reviewer@example.com
              team_id: team-123
      responses:
        '200':
          description: The invitations were accepted for processing.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/InviteUsersResponse'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '404':
          $ref: '#/components/responses/NotFound'
        '409':
          $ref: '#/components/responses/PortalRedirect'
        '422':
          $ref: '#/components/responses/ValidationError'
        '501':
          $ref: '#/components/responses/NotSupported'
        '503':
          $ref: '#/components/responses/Unavailable'
components:
  parameters:
    RequestId:
      name: request-id
      in: header
      required: false
      description: A unique request ID generated by the client for request tracing.
      schema:
        type: string
  schemas:
    InviteUsersRequest:
      type: object
      properties:
        emails:
          type: array
          items:
            type: string
            format: email
          minItems: 1
          maxItems: 200
        team_id:
          type: string
          nullable: true
          pattern: ^(?!\s*$)(?!\s*-\s*$).+
          description: A team in the caller's workspace.
      required:
        - emails
    InviteUsersResponse:
      type: object
      properties:
        message:
          type: string
        data:
          type: array
          items:
            type: object
      required:
        - message
        - data
    HttpError:
      type: object
      properties:
        detail:
          oneOf:
            - type: string
            - type: object
              additionalProperties: true
      required:
        - detail
    PortalRedirectError:
      type: object
      properties:
        detail:
          type: object
          properties:
            redirectTo:
              type: string
              format: uri
          required:
            - redirectTo
      required:
        - detail
    ValidationError:
      type: object
      properties:
        detail:
          type: array
          items:
            $ref: '#/components/schemas/ValidationErrorDetail'
      required:
        - detail
    ValidationErrorDetail:
      type: object
      properties:
        type:
          type: string
        loc:
          type: array
          items:
            oneOf:
              - type: string
              - type: integer
        msg:
          type: string
      required:
        - type
        - loc
        - msg
  responses:
    Unauthorized:
      description: The bearer credential or authenticated identity is invalid.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/HttpError'
    Forbidden:
      description: >-
        The caller is not an organization owner, lacks workspace context, or API
        access is not enabled for the organization.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/HttpError'
    NotFound:
      description: The member or team was not found in the caller's workspace.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/HttpError'
    PortalRedirect:
      description: >-
        The single-tenant identity flow returned another Qodo tenant host.
        Inspect `detail.redirectTo`, but do not forward credentials
        automatically.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/PortalRedirectError'
    ValidationError:
      description: Request validation failed.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ValidationError'
    NotSupported:
      description: The User management API is not supported for this deployment.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/HttpError'
    Unavailable:
      description: API availability or authorization could not be verified.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/HttpError'
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: sk-
      description: >-
        A personal `sk-` API key that belongs to an organization owner. Send it
        as `Authorization: Bearer sk-...`. See [Set up the User management
        API](/account-management/user-management-api).

````