> ## Documentation Index > Fetch the complete documentation index at: https://docs.app.strix.ai/llms.txt > Use this file to discover all available pages before exploring further. # Approve or deny a chat action > Decides one pending approval. Guarded operations are deletes, revocations, disconnects, removes, shares, role and organization changes, and actions that start work or reach outside Strix (scans, retests, fix pull requests, ticket pushes, invites). On `approve` the operation runs as the token's user inside the token's operation scopes and delegation, and the outcome is delivered to the agent with the next chat message. Returns 409 when the approval was already decided. ## OpenAPI ````yaml /openapi.json post /chat/{chatId}/approvals/{approvalId} openapi: 3.1.0 info: title: Strix API version: 1.0.0 description: >- Public REST API for the Strix autonomous penetration testing platform. Manage scans, vulnerabilities, assets, schedules, API tokens, and webhooks. servers: - url: /api/v1 description: Strix v1 API security: - BearerAuth: [] tags: - name: Scans description: Launch, monitor, and manage security scans. - name: Vulnerabilities description: View and triage discovered vulnerabilities. - name: Assets description: Domains and repositories registered for scanning. - name: Schedules description: Recurring scan schedules (Pro plan). - name: Search description: Search across issues, pentests, PR reviews, chats, assets and schedules. - name: Tokens description: Manage API tokens for authentication. - name: Webhooks description: Configure webhook subscriptions for real-time event notifications. - name: Organization description: Workspace configuration for the authenticated organization. - name: Members description: Manage organization members and roles. - name: Invitations description: List and revoke organization invitations. - name: PR Reviews description: Automated security review of pull requests. - name: Connectors description: Network connectors for scanning internal/private targets. - name: Knowledge description: >- Organization knowledge base: documents, policies, and repo profiles that steer the agent. - name: Uploads description: Upload source/code/documentation archives for whitebox scans. - name: Integrations description: Third-party integrations (GitLab, Bitbucket, ticketing). - name: Chat description: Conversational agent sessions. - name: Analytics description: Aggregate dashboard analytics. - name: Test Users description: >- Per-domain test accounts (with optional MFA) the agent authenticates as during scans. - name: License description: Self-hosted license state, entitlements, and aggregate usage. - name: Supply Chain description: >- SBOM inventory, supply-chain findings, scans, and policy for connected repositories. - name: CLI description: >- Device authorization endpoints that let the Strix CLI and coding agents sign in and receive an API token. - name: Billing description: Credit balance, agent-payable top-ups, and automatic top-up settings. - name: Workspaces description: List, create, and switch workspaces. - name: Asset Discovery description: >- Passive reconnaissance runs that map the organization's external attack surface, and the discovered-asset inventory they fill. - name: Containers description: >- Container registries, tracked images, image scans, findings, and SBOM components. - name: Run Logs description: Persisted engine logs and the diagnostics bundle of a self-hosted install. paths: /chat/{chatId}/approvals/{approvalId}: post: tags: - Chat summary: Approve or deny a chat action description: >- Decides one pending approval. Guarded operations are deletes, revocations, disconnects, removes, shares, role and organization changes, and actions that start work or reach outside Strix (scans, retests, fix pull requests, ticket pushes, invites). On `approve` the operation runs as the token's user inside the token's operation scopes and delegation, and the outcome is delivered to the agent with the next chat message. Returns 409 when the approval was already decided. operationId: decideChatActionApproval parameters: - name: chatId in: path required: true description: Chat id. schema: type: string format: uuid - name: approvalId in: path required: true description: Approval id. schema: type: string format: uuid requestBody: required: true content: application/json: schema: type: object properties: decision: type: string description: >- `approve` runs the guarded operation; `deny` records the refusal and tells the agent. enum: - approve - deny required: - decision responses: '200': description: The decided approval. content: application/json: schema: type: object properties: approval: $ref: '#/components/schemas/ChatActionApproval' required: - approval '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' '409': $ref: '#/components/responses/Conflict' '500': $ref: '#/components/responses/InternalError' security: - BearerAuth: - chat:write components: schemas: ChatActionApproval: type: object properties: id: type: string format: uuid chat_id: type: string format: uuid organization_id: type: string tool_name: type: string description: The chat API tool awaiting a decision, without the strix_ prefix. arguments: type: object requested_by_user_id: type: string status: type: string enum: - pending - running - succeeded - failed - denied - expired result: description: The tool outcome once the row is succeeded or failed. type: - object - 'null' decided_by_user_id: type: - string - 'null' decided_at: type: - string - 'null' format: date-time created_at: type: string format: date-time expires_at: type: - string - 'null' format: date-time description: >- Null for approvals created after the expiry was removed. Older approvals carried a 30 minute expiry and may still hold a timestamp. required: - id - chat_id - organization_id - tool_name - arguments - requested_by_user_id - status - created_at - expires_at ErrorResponse: type: object properties: detail: type: string description: Human-readable explanation of the error. code: type: string description: >- Stable machine-readable error code. `insufficient_scope` means the token does not hold the scope that this endpoint requires. required_scope: $ref: '#/components/schemas/ApiV1Scope' description: >- Scope that the caller must add to the token. Returned with the `insufficient_scope` code. docs: type: string format: uri description: Documentation page that explains how to resolve the error. hint: type: string description: >- One instruction that resolves the error. For `insufficient_scope`, a CLI session gets the `strix cloud session scopes set full` or `strix cloud login --scope-profile full` command, and an API token gets the settings page where the user creates a token with the scope. When the owner's role cannot hold the scope, the hint asks for a role change instead. required: - detail ApiV1Scope: type: string enum: - scans:read - scans:write - vulnerabilities:read - vulnerabilities:write - dependencies:read - schedules:read - schedules:write - assets:read - assets:write - organizations:read - organizations:write - members:read - members:write - invitations:read - invitations:write - webhooks:read - webhooks:write - tokens:write - audit:read - pr_reviews:read - pr_reviews:write - connectors:read - connectors:write - knowledge:read - knowledge:write - uploads:write - integrations:read - integrations:write - chat:read - chat:write - scans:message - analytics:read - llm:read - llm:write - test_users:read - test_users:write - discovery:read - discovery:write - license:read - supply_chain:read - supply_chain:write - billing:read - billing:write - containers:read - containers:write - logs:read responses: BadRequest: description: Bad request. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' Unauthorized: description: Missing or invalid API token. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' Forbidden: description: >- Insufficient permissions or missing scope. A missing scope returns the `insufficient_scope` code, the `required_scope` field, and a `hint` with the command or page that grants the scope, so a client can request the correct scope and retry. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' NotFound: description: Resource not found. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' Conflict: description: Conflict. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' InternalError: description: Internal server error. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' securitySchemes: BearerAuth: type: http scheme: bearer description: >- API token obtained from the Tokens endpoint or CLI device login. Include as `Authorization: Bearer `. Requests made with a managed CLI session also include `X-Strix-Workspace: ` to pin a process to the workspace it started in; recovery endpoints report the current workspace after a concurrent switch. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.