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

# List Extract workflows

> List active Extract chat workflow types.

Active `extract-*` chat types for the create-chat picker. Not the future pipeline-builder feature. Bare array, not paginated.


## OpenAPI

````yaml GET /api/v2/workflows/
openapi: 3.1.0
info:
  title: Abacus Docs API
  version: 1.0.0
  description: |
    REST + SSE surface for Abacus Docs on the same host as the web app
    (`https://abacusdocs.com`). Paths are `/api/v2/…`.

    Authenticate with an organisation API key (`sk-abacus-*`) as a Bearer
    token, or an Auth0 access token. Cross-tenant reads return **404**, not
    403. Page-based lists use `?page=` and `?page_size=`.

    Extraction, reprocess, schema tests, and chat turns spend credits.
    See the help centre Credits pages for rates.
  contact:
    name: Abacus Docs
    url: https://abacusdocs.com/contact
servers:
  - url: https://abacusdocs.com
    description: Production (Extract)
security: []
paths:
  /api/v2/workflows/:
    get:
      tags:
        - v2/workflows
      summary: List active Extract workflows
      description: >-
        Returns the active ``extract-*`` workflow definitions for the
        chat-create picker, ordered by ``sort_order`` then ``slug``. Excludes
        inactive rows and any non-Extract workflow (notably Deep Reader's
        ``document-intelligence``). Bare array — the catalog is small and
        admin-curated, so it is not paginated.
      operationId: v2_workflows_list
      responses:
        '200':
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/Workflow'
          description: ''
      security:
        - extractApiKey: []
        - bearerAuth: []
        - cookieAuth: []
components:
  schemas:
    Workflow:
      type: object
      description: |-
        One row in the Extract workflow picker.

        Fields:
            slug: Stable identifier; matches ``Chat.workflow_type`` values and is
                what the SPA sends back on chat create / ``PATCH`` (e.g.
                ``"extract-batch-analysis"``).
            display_name: Human-readable label for the picker tile.
            description: Short blurb shown under the label. May be empty.
            sort_order: Display order (ascending). The list endpoint already
                returns rows sorted by this, but it is surfaced so the SPA can
                re-sort after client-side filtering if needed. The model's help
                text documents this field as part of the API contract.

        ``icon`` from the plan is intentionally omitted: the ``Workflow`` model
        carries no icon field, so there is nothing to serialize (the SPA maps
        slug -> icon client-side).
      properties:
        slug:
          type: string
          pattern: ^[-a-zA-Z0-9_]+$
        display_name:
          type: string
        description:
          type: string
        sort_order:
          type: integer
      required:
        - description
        - display_name
        - slug
        - sort_order
  securitySchemes:
    extractApiKey:
      type: http
      scheme: bearer
      bearerFormat: API Key
      description: |
        Organisation API key from Settings → API / `/api/keys/`. The secret is
        shown once. Send `Authorization: Bearer sk-abacus-…`. One active key
        per organisation. Ingest (`/api/v2/ingest/*`) refuses API keys — that
        surface is Auth0-only with `ingest:read` / `ingest:write` scopes.
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >
        Auth0 access token for a signed-in user. Send `Authorization: Bearer
        <token>`.

        The SPA and desktop agent use this. Prefer an organisation API key for

        server-to-server integrations.
    cookieAuth:
      type: apiKey
      in: cookie
      name: sessionid
      description: |
        Django session cookie from a browser login. Present so the web app can
        call `/api/v2` without a header. Do not rely on this for integrations.

````