> ## Documentation Index > Fetch the complete documentation index at: https://docs.mixpeek.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Respond To Confirmation > Respond to a pending confirmation for a write operation. When the agent requests a write operation (create, update, delete), the stream pauses and emits a `confirmation_required` event. The user must call this endpoint to approve or deny the action. After responding, this endpoint returns a new SSE stream that continues the agent's execution from where it paused. ## Confirmation Workflow 1. User sends message via POST /sessions/{id}/messages 2. Agent proposes a write operation 3. Stream emits `confirmation_required` event with `confirmation_id` 4. User calls this endpoint with `approved: true/false` 5. This endpoint returns SSE stream continuing the agent's work 6. If approved, agent executes the tool and continues 7. If denied, agent acknowledges and continues without executing ## Confirmation Expiration Confirmations expire after 5 minutes. Attempting to respond to an expired confirmation returns a 400 error. Args: request: FastAPI request with tenant context session_id: Session identifier confirmation_id: Confirmation identifier from `confirmation_required` event payload: Approval/denial decision Returns: StreamingResponse with SSE events (continuation of agent execution) Raises: NotFoundError: If session or confirmation not found ValidationError: If confirmation already processed or expired Example: ```bash # Approve a pending action curl -N -X POST http://localhost:8000/v1/agents/sessions/ses_abc/confirmations/conf_xyz \ -H "Authorization: Bearer {api_key}" \ -H "X-Namespace: {namespace_id}" \ -H "Content-Type: application/json" \ -d '{"approved": true}' # SSE Output (continuation): event: tool_result data: {"tool_name": "delete_collection", "success": true, "result": {...}} event: token data: {"content": "I've deleted the collection as requested."} event: done data: {} ``` ## OpenAPI ````yaml post /v1/agents/sessions/{session_id}/confirmations/{confirmation_id} openapi: 3.1.0 info: title: Mixpeek API description: >- This is the Mixpeek API, providing access to various endpoints for data processing and retrieval. termsOfService: https://mixpeek.com/terms contact: name: Mixpeek Support url: https://mixpeek.com/contact email: info@mixpeek.com version: '0.82' servers: - url: https://api.mixpeek.com description: Production security: [] paths: /v1/agents/sessions/{session_id}/confirmations/{confirmation_id}: post: tags: - Agent Sessions summary: Respond To Confirmation description: |- Respond to a pending confirmation for a write operation. When the agent requests a write operation (create, update, delete), the stream pauses and emits a `confirmation_required` event. The user must call this endpoint to approve or deny the action. After responding, this endpoint returns a new SSE stream that continues the agent's execution from where it paused. ## Confirmation Workflow 1. User sends message via POST /sessions/{id}/messages 2. Agent proposes a write operation 3. Stream emits `confirmation_required` event with `confirmation_id` 4. User calls this endpoint with `approved: true/false` 5. This endpoint returns SSE stream continuing the agent's work 6. If approved, agent executes the tool and continues 7. If denied, agent acknowledges and continues without executing ## Confirmation Expiration Confirmations expire after 5 minutes. Attempting to respond to an expired confirmation returns a 400 error. Args: request: FastAPI request with tenant context session_id: Session identifier confirmation_id: Confirmation identifier from `confirmation_required` event payload: Approval/denial decision Returns: StreamingResponse with SSE events (continuation of agent execution) Raises: NotFoundError: If session or confirmation not found ValidationError: If confirmation already processed or expired Example: ```bash # Approve a pending action curl -N -X POST http://localhost:8000/v1/agents/sessions/ses_abc/confirmations/conf_xyz \ -H "Authorization: Bearer {api_key}" \ -H "X-Namespace: {namespace_id}" \ -H "Content-Type: application/json" \ -d '{"approved": true}' # SSE Output (continuation): event: tool_result data: {"tool_name": "delete_collection", "success": true, "result": {...}} event: token data: {"content": "I've deleted the collection as requested."} event: done data: {} ``` operationId: >- respond_to_confirmation_v1_agents_sessions__session_id__confirmations__confirmation_id__post parameters: - name: session_id in: path required: true schema: type: string description: Session ID title: Session Id description: Session ID - name: confirmation_id in: path required: true schema: type: string description: Confirmation ID title: Confirmation Id description: Confirmation ID requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/ConfirmationRequest' responses: '200': description: Successful Response content: application/json: schema: {} '400': description: Bad Request content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '403': description: Forbidden content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: Not Found content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' '500': description: Internal Server Error content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' components: schemas: ConfirmationRequest: properties: approved: type: boolean title: Approved description: True to approve, False to deny the action type: object required: - approved title: ConfirmationRequest description: Request to approve or deny a pending confirmation. ErrorResponse: properties: success: type: boolean title: Success description: Always false for error responses default: false status: type: integer title: Status description: HTTP status code for this error error: $ref: '#/components/schemas/ErrorDetail' description: Error details payload type: object required: - status - error title: ErrorResponse description: Error response model. examples: - error: details: id: ns_123 resource: namespace message: Namespace not found type: NotFoundError status: 404 success: false HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' type: array title: Detail type: object title: HTTPValidationError ErrorDetail: properties: message: type: string title: Message description: Human-readable error message type: type: string title: Type description: Stable error type identifier (machine-readable) code: anyOf: - type: string - type: 'null' title: Code description: >- Fine-grained error code for programmatic handling (e.g., namespace_name_taken, feature_extractor_not_found). Present only when consumers may need to branch on a specific error condition. details: anyOf: - additionalProperties: true type: object - type: 'null' title: Details description: >- Optional structured details to help debugging (validation errors, IDs, etc.) type: object required: - message - type title: ErrorDetail description: Error detail model. ValidationError: properties: loc: items: anyOf: - type: string - type: integer type: array title: Location msg: type: string title: Message type: type: string title: Error Type input: title: Input ctx: type: object title: Context type: object required: - loc - msg - type title: ValidationError ````