> ## Documentation Index > Fetch the complete documentation index at: https://docs.duvo.ai/llms.txt > Use this file to discover all available pages before exploring further. # List Config Fields > Read an automation's module config fields (its Policy), grouped by section in catalog order, with each field's current value, default, and fill provenance. ## OpenAPI ````yaml https://api.duvo.ai/v2/documentation/mintlify.json get /v2/automations/{automation_id}/config-fields openapi: 3.0.3 info: title: Duvo Public API description: >- Public API for programmatic access to Duvo. Authenticate with API keys created in the Duvo dashboard. ## Rate limits Requests are counted per API key. Every response advertises the quota with the IETF RateLimit fields, so a client can self-throttle without waiting for a rejection: - `RateLimit-Policy: "default";q=;w=` — the policy in force: `q` requests per `w` seconds. - `RateLimit: "default";r=;t=` — the live state: `r` requests left, quota resetting in `t` seconds. - Read the quota from the headers rather than hard-coding it; it differs per environment. - The same numbers are also sent as `ratelimit-limit`, `ratelimit-remaining` and `ratelimit-reset`. Once the quota is exhausted the API answers `429 Too Many Requests` with `Retry-After` set to the seconds to wait; honor it instead of retrying immediately. version: 1.0.0 servers: - url: https://api.duvo.ai description: Production server security: [] tags: - name: Runs description: Start, monitor, and manage agent runs (Runs in the Duvo UI) - name: Sandboxes description: Create sandboxes and upload files for agent runs - name: Queues description: Manage queues and their agent bindings - name: Cases description: Create, list, and manage cases and their labels within queues - name: Case Approvals description: Submit decisions on pending case approval requests issued by an agent run - name: Case Attachments description: Upload, list, download, and remove the files attached to a case - name: Automations description: >- List and manage automations — the workspace container that groups the agents and queues making up one end-to-end process - name: Agents description: Create and manage agents for automation workloads - name: Revisions description: Create and manage agent revisions — the underlying Setup for an Agent - name: Agent Folders description: Organize agents into folders - name: Agent Memory description: Read an agent's memory files (the Memory feature in the Duvo UI) - name: Suggestions description: >- List, apply, and dismiss an Agent's improvement suggestions (the suggestions inbox in the Duvo UI) - name: Notifications description: >- List, read, dismiss, and clear the authenticated user's team notifications (the Notification Center in the Duvo UI) - name: Schedules description: List schedules configured for an agent - name: Duvo Pulse description: >- Create, list, iterate on, and delete Duvo Pulse dashboards — live, agent-generated visualizations of your Duvo data - name: Case Triggers description: >- Configure case triggers that automatically dispatch agent runs (Runs in the Duvo UI) for cases added to a queue - name: Triggers description: >- Configure event triggers that start a Run automatically when an external event fires (e.g. an email arrives, a Linear issue is created, or a file changes in Google Drive) - name: Skills description: Manage team and system skills (reusable knowledge packs). - name: Files description: Manage team files. - name: Plugins description: Discover plugins that can be referenced from a revision. - name: Organizations description: Inspect organizations you belong to and the teams within them - name: Team description: Inspect the team and members associated with the API key - name: Invites description: >- Invite people to a team — one at a time or in bulk, scoped to a Clarity process or the whole team — and manage the team's shareable invite link - name: Integrations description: Browse the team's catalog of available integration types - name: Connections description: Manage your connected integrations - name: Credentials description: >- Manage logins (domain + username + password + TOTP) used by agents to sign in to websites and desktop applications, and attach them to assignment revisions - name: Secrets description: >- Manage env-var secrets injected into runs, and attach them to assignment revisions. Only metadata is exposed; values are never returned - name: Revision Integrations description: >- Attach integrations to assignment revisions, pin specific connections, and link queues - name: ClarityV2 description: >- Manage Clarity v2 process snapshots, automation proposals, and the extra-capture-request follow-up loop paths: /v2/automations/{automation_id}/config-fields: get: tags: - Automations summary: List Config Fields description: >- Read an automation's module config fields (its Policy), grouped by section in catalog order, with each field's current value, default, and fill provenance. operationId: listConfigFields parameters: - schema: type: string format: uuid in: path name: automation_id required: true description: The automation's unique identifier responses: '200': description: Default Response content: application/json: schema: type: object properties: sections: type: array items: type: object properties: section: type: string description: Section name fields: type: array items: type: object properties: id: type: string description: Unique config field identifier key: type: string description: Stable field key referenced by the automation section: type: string description: Catalog section this field is grouped under position: type: number description: Order of the field within its section question: type: string description: The setup question shown for this field type: type: string enum: - freeText - identifier - number - select - multiSelect - list - orderedList - personList - table - compound - sourcePointer description: >- Value type (e.g. freeText, number, select, compound) type_config: nullable: true description: >- Per-type options (e.g. select choices, number unit/min), or null type: object additionalProperties: $ref: >- #/components/schemas/AutomationConfigJsonValue bindings: type: array items: type: string enum: - context - parameter - tool - structural - readOnly description: >- How the value reaches the automation (context, parameter, tool) required: type: boolean description: Whether the field must be filled locked: type: boolean description: Whether the value is locked from editing fill_mode: type: string enum: - interview - setup - module_default description: >- How the field is filled (interview, setup, module_default) value: nullable: true description: The current answer, or null when unfilled allOf: - $ref: >- #/components/schemas/AutomationConfigJsonValue default_value: nullable: true description: The module default value, or null allOf: - $ref: >- #/components/schemas/AutomationConfigJsonValue status: type: string enum: - default - filled description: >- 'filled' when the field has a value, else 'default' provenance: nullable: true description: >- Who filled the value and how, or null when unfilled type: object properties: filled_via: type: string enum: - manual - interview - template_default - org_default - ask_duvo description: >- How the value was filled (e.g. interview, setup, manual) filled_by_user_id: nullable: true description: >- ID of the user who filled the value, when a person did type: string filled_by_name: nullable: true description: >- Display name of the user who filled the value type: string filled_at: type: string description: >- ISO 8601 timestamp when the value was filled source_capture_id: nullable: true description: >- ID of the capture the value was extracted from, when applicable type: string required: - filled_via - filled_by_user_id - filled_by_name - filled_at - source_capture_id additionalProperties: false required: - id - key - section - position - question - type - type_config - bindings - required - locked - fill_mode - value - default_value - status - provenance additionalProperties: false description: Fields in this section, in catalog order required: - section - fields additionalProperties: false description: Config fields grouped by section, in catalog order filled_count: type: number description: Number of fields that have a value required_count: type: number description: Number of required fields required_filled_count: type: number description: Number of required fields that have a value total_count: type: number description: Total number of fields required: - sections - filled_count - required_count - required_filled_count - total_count additionalProperties: false '401': description: Default Response content: application/json: schema: type: object properties: error: type: string required: - error additionalProperties: false '403': description: Default Response content: application/json: schema: type: object properties: error: type: string required: - error additionalProperties: false '404': description: Default Response content: application/json: schema: type: object properties: error: type: string required: - error additionalProperties: false '500': description: Default Response content: application/json: schema: type: object properties: error: type: string required: - error additionalProperties: false security: - bearerAuth: [] components: schemas: AutomationConfigJsonValue: anyOf: - type: string nullable: true - type: number - type: boolean - type: array items: $ref: '#/components/schemas/AutomationConfigJsonValue' - type: object additionalProperties: $ref: '#/components/schemas/AutomationConfigJsonValue' nullable: true securitySchemes: bearerAuth: type: http scheme: bearer description: API key authentication. Get your API key from the Duvo dashboard. ````