> ## Documentation Index > Fetch the complete documentation index at: https://docs.agentsfleet.net/llms.txt > Use this file to discover all available pages before exploring further. # Approve a pending request > Approves a pending request. If two callers resolve it, the first result wins. Other callers receive 409 with the existing result and resolver. ## OpenAPI ````yaml https://raw.githubusercontent.com/agentsfleet/agentsfleet/main/public/openapi.json post /v1/workspaces/{workspace_id}/approvals/{gate_id}:approve openapi: 3.1.0 info: title: agentsfleet Control Plane API version: 1.0.0 description: API for managing workspaces, fleets, triggers, and runs. contact: name: agentsfleet url: https://agentsfleet.net servers: - url: https://api.agentsfleet.net description: Production security: - BearerAuth: [] tags: - name: Health description: System status and readiness probes x-mintlify: navigation: Health - name: Authentication description: Command Line Interface (CLI) sign-in sessions and GitHub sign-in x-mintlify: navigation: Authentication - name: Workspaces description: Create and manage workspaces x-mintlify: navigation: Workspaces - name: Tenant description: Manage tenant provider settings and models x-mintlify: navigation: Tenant - name: auth-identity-events description: >- Process signed account events from Clerk. This route is not for customer fleets. x-mintlify: navigation: Auth Identity Events - name: Fleets description: Create, configure, and run fleets x-mintlify: navigation: Fleets - name: Schedules description: Manage and receive scheduled Fleet events x-mintlify: navigation: Schedules - name: Memory description: Read and search saved fleet memory x-mintlify: navigation: Memory - name: Secrets description: Manage named secrets for fleets in a workspace x-mintlify: navigation: Secrets - name: Admin description: Manage shared provider keys and models x-mintlify: navigation: Admin - name: Billing description: Read tenant balances and charge records x-mintlify: navigation: Billing - name: Integration Grants description: Manage fleet access to third-party services x-mintlify: navigation: Integration Grants - name: Connectors description: Connect workspaces to third-party providers x-mintlify: navigation: Connectors - name: Fleet Keys description: Manage keys that let external clients call a fleet x-mintlify: navigation: Fleet Keys - name: API Keys description: Manage tenant admin API keys x-mintlify: navigation: API Keys - name: Webhooks description: Receive signed events and approval decisions x-mintlify: navigation: Webhooks - name: Approvals description: List, inspect, and resolve pending approvals x-mintlify: navigation: Approvals - name: Fleet description: Enroll and manage runners x-mintlify: navigation: Fleet - name: Fleet Bundles description: Manage fleet source bundles in a workspace x-mintlify: navigation: Fleet Bundles - name: Fleet library description: Browse and add reusable fleet sources x-mintlify: navigation: Fleet library - name: Model Library description: List models available to the tenant x-mintlify: navigation: Model Library paths: /v1/workspaces/{workspace_id}/approvals/{gate_id}:approve: post: tags: - Approvals summary: Approve a pending request description: > Approves a pending request. If two callers resolve it, the first result wins. Other callers receive 409 with the existing result and resolver. operationId: approve_workspace_approval parameters: - name: workspace_id in: path required: true schema: type: string format: uuid - name: gate_id in: path required: true schema: type: string format: uuid requestBody: required: false content: application/json: schema: $ref: '#/components/schemas/ApprovalResolveBody' responses: '200': description: Resolved content: application/json: schema: $ref: '#/components/schemas/ApprovalResolveResponse' '401': $ref: '#/components/responses/Error' '403': $ref: '#/components/responses/Error' '404': $ref: '#/components/responses/Error' '409': description: Already resolved by another channel content: application/problem+json: schema: $ref: '#/components/schemas/ApprovalAlreadyResolvedResponse' components: schemas: ApprovalResolveBody: type: object properties: reason: type: string maxLength: 4096 description: Optional free-form note attached to the resolution. ApprovalResolveResponse: type: object required: - gate_id - action_id - outcome - resolved_at - resolved_by properties: gate_id: type: string format: uuid action_id: type: string format: uuid outcome: type: string enum: - approved - denied - timed_out - auto_killed resolved_at: type: integer format: int64 resolved_by: type: string ApprovalAlreadyResolvedResponse: description: > Error response for a request that was already resolved. The response includes the first result, time, and resolver. allOf: - $ref: '#/components/schemas/ErrorBody' - type: object required: - gate_id - outcome - resolved_at - resolved_by properties: gate_id: type: string format: uuid action_id: type: string format: uuid outcome: type: string enum: - approved - denied - timed_out - auto_killed resolved_at: type: integer format: int64 resolved_by: type: string ErrorBody: type: object description: RFC 7807 problem detail error response (application/problem+json) required: - docs_uri - title - detail - error_code - request_id properties: docs_uri: type: string format: uri description: Stable link to documentation for this error code example: https://docs.agentsfleet.net/api-reference/error-codes#UZ-AGT-009 title: type: string description: Short human-readable label, same for every occurrence of this code example: Fleet not found detail: type: string description: Instance-specific context describing what went wrong example: No fleet with id 'abc123' in this workspace. error_code: type: string description: Machine-readable error code example: UZ-AGT-009 request_id: type: string description: Correlation ID for this request current_state: type: string description: >- Resource state that blocked the requested change. Present only on 409 responses. example: paused user_message: type: string description: > Plain message safe to show to a user. Present only when an error defines one. Use `detail` or `title` when this field is absent. example: >- We couldn't find that Fleet. It may have been deleted, or the ID doesn't match one in this workspace. etag: type: string description: >- Resource version returned on 412 responses so the caller can refetch and retry. responses: Error: description: RFC 7807 problem detail error response content: application/problem+json: schema: $ref: '#/components/schemas/ErrorBody' securitySchemes: BearerAuth: type: http scheme: bearer bearerFormat: JWT description: >- Obtain a token via the CLI auth flow (POST /v1/auth/sessions) or GitHub OAuth ````