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

# List Configs

> List saved configurations with pagination. Optionally filter by config type.



## OpenAPI

````yaml /openapi-extraction-v2.json get /api/v2/configs
openapi: 3.1.0
info:
  title: Nanonets V2 API
  description: >-
    Stateful document processing API with file management, reusable configs, and
    JSON-body endpoints for parse, extract, and classify operations.


    **Key differences from V1:**

    - JSON request bodies instead of multipart/form-data

    - Upload files once via `POST /files`, then reference them with
    `file://<uuid>` URIs

    - Save and reuse processing configurations via `config://<uuid>` URIs

    - Batch processing via list inputs on async endpoints (up to 50 items)

    - Document classification with `document` and `split` modes
  version: 2.0.0
  contact:
    name: Nanonets Support
    email: info@nanonets.com
servers:
  - url: https://extraction-api.nanonets.com
    description: Production
security:
  - BearerAuth: []
paths:
  /api/v2/configs:
    get:
      tags:
        - Configuration Management
      summary: List Configs
      description: >-
        List saved configurations with pagination. Optionally filter by config
        type.
      operationId: v2_list_configs
      parameters:
        - name: type
          in: query
          required: false
          description: Filter by config type
          schema:
            type: string
            enum:
              - parse
              - extract
              - classify
        - name: page
          in: query
          schema:
            type: integer
            minimum: 1
            default: 1
        - name: page_size
          in: query
          schema:
            type: integer
            minimum: 1
            maximum: 100
            default: 50
      responses:
        '200':
          description: List of configs
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ConfigListResponse'
        '401':
          $ref: '#/components/responses/Unauthorized'
components:
  schemas:
    ConfigListResponse:
      type: object
      required:
        - success
        - configs
      properties:
        success:
          type: boolean
        configs:
          type: array
          items:
            $ref: '#/components/schemas/ConfigResponse'
        total:
          type: integer
        page:
          type: integer
        page_size:
          type: integer
    ConfigResponse:
      type: object
      required:
        - success
        - config_id
        - name
        - type
        - params
      properties:
        success:
          type: boolean
        config_id:
          type: string
          description: '`config://<uuid>` URI'
          example: config://b2c3d4e5-f6a7-8901-bcde-f12345678901
        name:
          type: string
        type:
          type: string
          enum:
            - parse
            - extract
            - classify
        params:
          type: object
        created_at:
          type: string
          format: date-time
        updated_at:
          type: string
          format: date-time
    ErrorResponse:
      type: object
      properties:
        detail:
          type: string
  responses:
    Unauthorized:
      description: Invalid or missing API key
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      description: 'API key as Bearer token: `Authorization: Bearer YOUR_API_KEY`'

````