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

# List Users

> List members of an organization.



## OpenAPI

````yaml GET /orgs/{org_id}/iam/users
openapi: 3.1.0
info:
  title: Timbal Platform API
  description: Public API documentation for the Timbal platform
  license:
    name: ''
  version: 2.0.0
servers:
  - url: https://api.timbal.ai
    description: Production
  - url: https://api.dev.timbal.ai
    description: Development
security: []
tags:
  - name: ace
    description: Action Control Engine (ACE) operations
  - name: analytics
    description: Org and project analytics
  - name: billing
    description: Subscriptions, usage, and payment-related operations
  - name: content
    description: Re-sign stored content URLs
  - name: files
    description: File operations
  - name: iam
    description: IAM — actions, roles, users, and authorization introspection
  - name: k2
    description: Knowledge Bases v2 operations
  - name: orgs
    description: Organization operations
  - name: projects
    description: Project operations
  - name: runs
    description: Execution operations
  - name: templates
    description: Public project template catalog
  - name: users
    description: Authenticated user profile
paths:
  /orgs/{org_id}/iam/users:
    get:
      tags:
        - iam
      description: List members of an organization.
      operationId: handler
      parameters:
        - name: org_id
          in: path
          required: true
          schema:
            type: string
        - name: q
          in: query
          description: Optional case-insensitive substring filter on user name or email.
          required: false
          schema:
            type:
              - string
              - 'null'
        - name: page_token
          in: query
          description: |-
            Page token for pagination. Pass back the `next_page_token` from the
            previous response.
          required: false
          schema:
            type:
              - string
              - 'null'
      responses:
        '200':
          description: Organization members
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ListOrgUsersResBody'
        '403':
          description: Insufficient permissions
      security:
        - bearer_auth: []
components:
  schemas:
    ListOrgUsersResBody:
      type: object
      required:
        - org_users
      properties:
        next_page_token:
          type:
            - string
            - 'null'
          description: Token to fetch the next page, or null if this is the last page
        org_users:
          type: array
          items:
            $ref: '#/components/schemas/OrgUser'
          description: List of users in the organization
    OrgUser:
      type: object
      required:
        - email
        - role
        - roles
        - pending
      properties:
        email:
          type: string
          description: User's email address
        id:
          type:
            - string
            - 'null'
          description: |-
            Unique user identifier. Null only for legacy pending invites created
            before invites allocated a user up front; use `pending` to detect
            not-yet-registered members.
        name:
          type:
            - string
            - 'null'
          description: User's display name
        pending:
          type: boolean
          description: >-
            True when the member was invited but hasn't completed signup yet.
            Such

            members can still have roles assigned ahead of their first login.
        photo_url:
          type:
            - string
            - 'null'
          description: URL of the user's profile photo
        role:
          type: string
          description: |-
            Legacy single-role text. Kept for backward compatibility; new
            integrations should rely on `roles`.
        roles:
          type: array
          items:
            $ref: '#/components/schemas/RolePreview'
          description: >-
            Roles currently attached to this membership. Empty for members with
            no

            role attachments (including freshly invited users).
    RolePreview:
      type: object
      description: |-
        Compact role record returned by listing endpoints. Fetch a single
        role to retrieve the full grant set.
      required:
        - id
        - name
        - source
        - created_at
        - updated_at
      properties:
        created_at:
          type: string
          format: date-time
        description:
          type:
            - string
            - 'null'
        id:
          type: string
        name:
          type: string
          description: |-
            Role name. Unique per `(org_id)` for custom roles, globally unique
            for system roles.
        source:
          $ref: '#/components/schemas/RoleSource'
        updated_at:
          type: string
          format: date-time
    RoleSource:
      type: string
      description: |-
        Whether a role is a built-in preset or defined by the organization.
        `system` roles are read-only; `custom` roles can be edited or deleted
        by an organization admin.
      enum:
        - system
        - custom
  securitySchemes:
    bearer_auth:
      type: http
      scheme: bearer
      description: >-
        Timbal API key. Obtain your API key from the Timbal platform settings.
        See [Authentication](/api-reference/authentication) for more
        information.

````