openapi: 3.1.0
info:
  title: Quenza ArchiveClient ListMember API
  version: 1.0.0
  description: The Quenza API allows you to integrate your systems with Quenza — manage clients, sync data, and automate workflows. Authenticate using a Bearer token from your workspace settings under Developer Tools → API Token.
servers:
- url: https://developers.quenza.com/v1
security:
- http: []
tags:
- name: ListMember
paths:
  /members:
    get:
      operationId: developers.v1.members.list
      description: Returns a paginated list of all team members (professionals) in the workspace, including pending and suspended members.
      summary: List members
      tags:
      - ListMember
      parameters:
      - name: offset
        in: query
        description: Number of items to skip.
        schema:
          type: integer
          default: 0
        example: 0
      - name: limit
        in: query
        description: 'Number of items to return per request. Max: 100.'
        schema:
          type: integer
          default: 20
        example: 20
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: array
                    items:
                      $ref: '#/components/schemas/ProfessionalResource'
                  meta:
                    type: object
                    properties:
                      limit:
                        type: integer
                      offset:
                        type: integer
                      total:
                        type: integer
                    required:
                    - limit
                    - offset
                    - total
                  links:
                    type: object
                    properties:
                      next:
                        type:
                        - string
                        - 'null'
                      prev:
                        type:
                        - string
                        - 'null'
                    required:
                    - next
                    - prev
                required:
                - data
                - meta
                - links
        '401':
          $ref: '#/components/responses/AuthenticationException'
components:
  schemas:
    ProfessionalResource:
      type: object
      properties:
        id:
          type: string
        email:
          type: string
        first_name:
          type: string
        last_name:
          type: string
        status:
          type: string
        role:
          type: string
        timezone:
          type: string
        phone:
          type:
          - string
          - 'null'
        company:
          type:
          - string
          - 'null'
        website:
          type:
          - string
          - 'null'
        address:
          type:
          - string
          - 'null'
        city:
          type:
          - string
          - 'null'
        state:
          type:
          - string
          - 'null'
        country_code:
          type:
          - string
          - 'null'
        invited_at:
          type: string
        invitation_accepted_at:
          type: string
        created_at:
          type: string
        updated_at:
          type: string
      required:
      - id
      - email
      - first_name
      - last_name
      - status
      - role
      - timezone
      - phone
      - company
      - website
      - address
      - city
      - state
      - country_code
      - invited_at
      - invitation_accepted_at
      - created_at
      - updated_at
      title: ProfessionalResource
  responses:
    AuthenticationException:
      description: Unauthenticated
      content:
        application/json:
          schema:
            type: object
            properties:
              message:
                type: string
                description: Error overview.
            required:
            - message
  securitySchemes:
    http:
      type: http
      description: 'Authenticate using a **Bearer token** in the `Authorization` header:


        ```

        Authorization: Bearer {your-token}

        ```


        You can generate or regenerate your API token in your Quenza workspace under

        **Settings → Developer Tools → API Token**.'
      scheme: bearer