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

> ## Agent Instructions
> Flowsign is one word with a lowercase s.
> The REST API base URL is https://my.flowsign.app and every endpoint lives under /api/v1.
> When answering API questions, cite the HTTP method and endpoint path.
> API access needs the Enterprise plan and an API key with the API access permission.

# List signing group members

> Returns the members of a signing group, oldest first. Requires canManageSigningGroups.



## OpenAPI

````yaml /api-reference/openapi.json get /api/v1/signing-groups/{groupId}/members
openapi: 3.0.3
info:
  title: Flowsign API
  version: 1.0.0
  description: >-
    Public v1 API for Flowsign. Every endpoint is authenticated with a Bearer
    API key (prefix `fsk_`). Errors use `{ error, details? }`; success responses
    wrap payload data as `{ data }`.


    An organisation is divided into workspaces. A key is issued for one
    workspace and acts there on every request (see `GET /api/v1/workspaces`);
    `X-Workspace-Id` is optional and may only name that workspace. Packages,
    templates, contacts and members are scoped to the key's workspace.
servers:
  - url: https://my.flowsign.app
    description: Production
security:
  - ApiKey: []
paths:
  /api/v1/signing-groups/{groupId}/members:
    get:
      tags:
        - Signing groups
      summary: List signing group members
      description: >-
        Returns the members of a signing group, oldest first. Requires
        canManageSigningGroups.
      operationId: getSigning-groupsByGroupIdMembers
      parameters:
        - schema:
            type: string
          required: true
          name: groupId
          in: path
        - schema:
            type: string
            description: >-
              The workspace the key was issued for, as returned by `GET
              /api/v1/workspaces`. Optional: omitting it acts in the key's
              workspace, and any other id is rejected with 401.
          required: false
          name: x-workspace-id
          in: header
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: array
                    items:
                      type: object
                      properties:
                        id:
                          type: string
                          description: The member's user id.
                          example: 3f9d2c1e-7b4a-4e8f-9c21-5a6b7d8e9f01
                        email:
                          type: string
                          description: The member's email address.
                          example: jane.ahu@example.co.nz
                        displayName:
                          type: string
                          nullable: true
                          description: >-
                            The member's display name. Null when they have not
                            set one.
                          example: Jane Ahu
                        deactivated:
                          type: boolean
                          description: >-
                            True when the member's user account has been
                            deactivated in the organisation. Deactivated members
                            stay listed until removed and cannot be added again.
                          example: false
                        joinedAt:
                          type: string
                          description: When the member was added to the group (ISO 8601).
                          example: '2026-07-21T22:12:03.000Z'
                      required:
                        - id
                        - email
                        - displayName
                        - deactivated
                        - joinedAt
                    description: The group's members, oldest first.
                required:
                  - data
        '401':
          description: Missing or invalid API key
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '402':
          description: Caller's plan does not include this feature (publicApi / webhooks)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '403':
          description: API key present but caller lacks the required permission
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '404':
          description: No signing group with that id in the workspace
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '422':
          description: Request failed schema validation; details keyed by field
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '429':
          description: Rate limit exceeded; see `Retry-After`
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    Error:
      type: object
      properties:
        error:
          type: string
          description: What went wrong, in plain words.
          example: 'Missing permission: canSendPackages'
        details:
          type: object
          additionalProperties:
            type: array
            items:
              type: string
          description: >-
            Validation problems keyed by field path. Present only on 422
            responses.
          example:
            recipients.0.email:
              - Invalid email
      required:
        - error
  securitySchemes:
    ApiKey:
      type: http
      scheme: bearer
      bearerFormat: fsk_*

````