> ## 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.

# Get the account behind a key

> Returns the organisation, workspace, API key and user behind the call. Integrations use it to label a connection.



## OpenAPI

````yaml /api-reference/openapi.json get /api/v1/account
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/account:
    get:
      tags:
        - Account
      summary: Get the account behind a key
      description: >-
        Returns the organisation, workspace, API key and user behind the call.
        Integrations use it to label a connection.
      operationId: getAccount
      parameters:
        - 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: object
                    properties:
                      organization:
                        type: object
                        properties:
                          id:
                            type: string
                            description: Organisation id.
                            example: 7c2e5b1a-9d3f-4a6e-8b0c-1d2e3f4a5b6c
                          name:
                            type: string
                            description: Organisation name.
                            example: Studio Phoenix Limited
                        required:
                          - id
                          - name
                      workspace:
                        type: object
                        properties:
                          id:
                            type: string
                            description: Id of the workspace this call acted in.
                            example: cmg1gz5qk0001v8p9a3m2ud7h
                          name:
                            type: string
                            description: Workspace name.
                            example: Sales
                        required:
                          - id
                          - name
                      key:
                        type: object
                        nullable: true
                        properties:
                          id:
                            type: string
                            description: API key id.
                            example: cmg1h2c8n0002v8p9e5w1kf9j
                          name:
                            type: string
                            description: The label the key was given when it was issued.
                            example: Zapier connection
                          role:
                            type: string
                            description: >-
                              Name of the permission profile the key acts as,
                              for example a system role such as Admin, Sender or
                              Viewer, or a custom role.
                            example: Sender
                        required:
                          - id
                          - name
                          - role
                        description: >-
                          The API key the call was made with. Null when the call
                          was made with a signed-in session rather than a key.
                      user:
                        type: object
                        properties:
                          id:
                            type: string
                            description: >-
                              Id of the user work is attributed to: the key's
                              issuer.
                            example: 3f9d2c1e-7b4a-4e8f-9c21-5a6b7d8e9f01
                          email:
                            type: string
                            description: That user's email address.
                            example: jane.ahu@example.co.nz
                        required:
                          - id
                          - email
                    required:
                      - organization
                      - workspace
                      - key
                      - user
                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'
        '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_*

````