> ## 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. # Approve Automation Proposal > Approve the automation proposal of a Module automation being set up, the same as the setup's Approve and build in the web app: it opens an Ask Duvo conversation that reads the proposal and the Policy, proposes which Agents, Queues and dashboards change, makes the changes once the user agrees there, and finishes the setup. Give the user the conversation's `url`; they answer Duvo's plan in it. `proposal_snapshot_id`, when given, must be the live proposal. A build already started is returned with status `already_started` rather than started twice. Refused with 409 when there is no live proposal, required Policy questions are open, or Ask Duvo isn't available to the team, and with 403 below Builder. Confirm with the user before calling: approving starts the build. ## OpenAPI ````yaml https://api.duvo.ai/v2/documentation/mintlify.json post /v2/automations/{automation_id}/setup/approve-proposal 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}/setup/approve-proposal: post: tags: - Automations summary: Approve Automation Proposal description: >- Approve the automation proposal of a Module automation being set up, the same as the setup's Approve and build in the web app: it opens an Ask Duvo conversation that reads the proposal and the Policy, proposes which Agents, Queues and dashboards change, makes the changes once the user agrees there, and finishes the setup. Give the user the conversation's `url`; they answer Duvo's plan in it. `proposal_snapshot_id`, when given, must be the live proposal. A build already started is returned with status `already_started` rather than started twice. Refused with 409 when there is no live proposal, required Policy questions are open, or Ask Duvo isn't available to the team, and with 403 below Builder. Confirm with the user before calling: approving starts the build. operationId: approveAutomationProposal parameters: - schema: type: string format: uuid in: path name: automation_id required: true description: Automation ID requestBody: required: false content: application/json: schema: type: object properties: proposal_snapshot_id: description: >- The automation proposal being approved. Must be the live proposal; leave out to approve whichever proposal is live. type: string format: uuid additionalProperties: false responses: '200': description: Default Response content: application/json: schema: type: object properties: build: type: object properties: status: type: string enum: - started - already_started description: >- `started`: the approval opened an Ask Duvo conversation that builds the automation. `already_started`: the approved proposal was handed to that conversation before, so nothing new started. chat_id: type: string format: uuid description: The Ask Duvo conversation building the automation. proposal_snapshot_id: nullable: true description: >- The approved automation proposal, or null when the build had already started. type: string format: uuid link: type: string description: >- Root-relative web-app path to the build conversation, where the user reads Duvo's plan and answers it. url: type: string description: The full web-app URL of `link`. required: - status - chat_id - proposal_snapshot_id - link - url additionalProperties: false required: - build additionalProperties: false '400': description: Default Response content: application/json: schema: type: object properties: error: type: string message: type: string code: type: string validationErrors: type: array items: type: object properties: field: type: string message: type: string required: - field - message additionalProperties: false required: - error additionalProperties: false '401': description: Default Response content: application/json: schema: type: object properties: error: type: string message: type: string code: type: string validationErrors: type: array items: type: object properties: field: type: string message: type: string required: - field - message additionalProperties: false required: - error additionalProperties: false '403': description: Default Response content: application/json: schema: type: object properties: error: type: string message: type: string code: type: string validationErrors: type: array items: type: object properties: field: type: string message: type: string required: - field - message additionalProperties: false required: - error additionalProperties: false '404': description: Default Response content: application/json: schema: type: object properties: error: type: string message: type: string code: type: string validationErrors: type: array items: type: object properties: field: type: string message: type: string required: - field - message additionalProperties: false required: - error additionalProperties: false '409': description: Default Response content: application/json: schema: type: object properties: error: type: string message: type: string code: type: string validationErrors: type: array items: type: object properties: field: type: string message: type: string required: - field - message additionalProperties: false required: - error additionalProperties: false '500': description: Default Response content: application/json: schema: type: object properties: error: type: string message: type: string code: type: string validationErrors: type: array items: type: object properties: field: type: string message: type: string required: - field - message additionalProperties: false required: - error additionalProperties: false security: - bearerAuth: [] components: securitySchemes: bearerAuth: type: http scheme: bearer description: API key authentication. Get your API key from the Duvo dashboard. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.