> ## Documentation Index > Fetch the complete documentation index at: https://docs.neo.projectdiscovery.io/llms.txt > Use this file to discover all available pages before exploring further. # Approve or decline a suspended tool call > Submits an approval decision for a task whose agent stream is suspended waiting for user input (e.g., plan approval, ask_question). - **approve**: resumes the agent with the provided metadata/answers. - **decline**: cancels the pending action. For suspended streams, the endpoint atomically transitions the stream from `suspended` to `resuming` (CAS guard) to prevent double-approve. For active streams with in-tool timeout approval (ask_question), the endpoint forwards the decision to the Bun agent's in-memory waiter. ## OpenAPI ````yaml https://neo.api.projectdiscovery.io/api/openapi.json post /api/v1/tasks/{id}/approve openapi: 3.1.0 info: contact: name: ProjectDiscovery url: https://neo.projectdiscovery.io description: Neo API Server - Security agent orchestration platform license: name: Apache 2.0 url: https://www.apache.org/licenses/LICENSE-2.0 title: Neo API version: 1.0.0 servers: - description: Production url: https://neo.api.projectdiscovery.io - description: Local development url: http://localhost:8080 security: [] tags: - description: Task execution and management name: Tasks - description: Agent listing and management name: Agents - description: Public agent directory name: Agent Directory - description: User file storage management name: Files - description: User working memory management name: Memory - description: Scheduled and recurring task management name: Schedules - description: Knowledge base and semantic search name: Knowledge - description: Encrypted user credentials and API keys name: Secrets - description: Neo API key management for programmatic access name: API Keys - description: User profile and account information name: User - description: Task and LLM usage tracking name: Usage - description: Bring Your Own Key provider management name: BYOK - description: Model discovery and capabilities name: Models - description: Third-party integrations name: Integrations - description: Skill knowledge documents for agent prompts name: Skills - description: Team management and member invitations name: Teams - description: Prompt library management and discovery name: Prompts - description: Slack bot integration for workspace installation and OAuth name: Slack - description: GitHub integration for PR reviews and repository management name: GitHub - description: Vulnerability issue tracking and management name: Issues - description: Subscription billing and plans name: Billing - description: Project management and member assignments name: Projects - description: SSH key pair generation and management for remote server access name: SSH Keys - description: Codebase structural analysis and mapping name: Codemaps - description: AI-generated codebase documentation and security analysis name: CodeWiki - description: Captured HTTP traffic query and replay name: Network Events paths: /api/v1/tasks/{id}/approve: post: tags: - Tasks summary: Approve or decline a suspended tool call description: | Submits an approval decision for a task whose agent stream is suspended waiting for user input (e.g., plan approval, ask_question). - **approve**: resumes the agent with the provided metadata/answers. - **decline**: cancels the pending action. For suspended streams, the endpoint atomically transitions the stream from `suspended` to `resuming` (CAS guard) to prevent double-approve. For active streams with in-tool timeout approval (ask_question), the endpoint forwards the decision to the Bun agent's in-memory waiter. operationId: post-v1-tasks-id-approve parameters: - description: Task ID in: path name: id required: true schema: format: uuid type: string requestBody: content: application/json: schema: $ref: '#/components/schemas/ApproveToolCallRequest' required: true responses: '200': content: application/json: schema: $ref: '#/components/schemas/ApproveToolCallResponse' description: Approval processed successfully '400': content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: Invalid request body or decision '401': content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: Unauthorized '403': content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: Not authorized to approve this task '404': content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: No stream found for this task '409': content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: No pending approval (already resumed or not suspended) security: - BearerAuth: [] - ApiKeyAuth: [] components: schemas: ApproveToolCallRequest: properties: agent_id: description: >- Agent ID to resume (optional, resolved from stream metadata if omitted) type: string decision: description: Whether to approve or decline the pending tool call enum: - approve - decline type: string metadata: additionalProperties: true description: >- Answers or additional data to pass to the resumed tool (e.g., ask_question answers) type: object run_id: description: Agent run ID (optional, resolved from stream metadata if omitted) type: string tool_call_id: description: Specific tool call ID to approve (for parallel subagent routing) type: string required: - decision type: object ApproveToolCallResponse: properties: error: description: Error message if approval failed type: string stream_id: description: ID of the resumed stream type: string success: type: boolean required: - success type: object ErrorResponse: properties: code: description: > Stable machine-readable error code — branch on this rather than matching the human `error`/`message` strings. Domain codes include `user_spending_cap_reached`, `project_spending_cap_reached`, and `insufficient_neo_credits`; otherwise it mirrors the error kind (e.g. `forbidden`, `invalid_request`, `not_exists`, `already_exists`). example: user_spending_cap_reached type: string error: example: Bad request type: string error_id: description: Correlation id for a specific error instance, when present. type: string kind: description: Coarse error category (e.g. "forbidden request", "invalid request"). example: forbidden request type: string message: description: | Human-readable detail (the kind prefixed to the error). For display, not for branching. type: string required: - error type: object securitySchemes: BearerAuth: bearerFormat: JWT description: JWT authentication token scheme: bearer type: http ApiKeyAuth: description: Neo API key (neo_sk_* prefix) in: header name: X-Api-Key type: apiKey ````