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//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:

# 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: {}

POST /v1/agents/sessions/{session_id}/confirmations/{confirmation_id}

Respond To Confirmation

cURL

curl --request POST \
  --url https://api.mixpeek.com/v1/agents/sessions/{session_id}/confirmations/{confirmation_id} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --header 'X-Namespace: <api-key>' \
  --data '
{
  "approved": true
}
'

400

{
  "status": 123,
  "error": {
    "message": "<string>",
    "type": "<string>",
    "code": "<string>",
    "details": {}
  },
  "success": false
}

Authorizations

Authorization · string · header · required

Mixpeek API key, sent as Authorization: Bearer mxp_sk_.... Create one in Studio under Settings → API Keys, or with an admin key via POST /v1/organizations/users/{user_email}/api-keys. A missing header returns 403; an invalid or revoked key returns 401.

X-Namespace · string · header · required

Namespace id (ns_...), not the namespace name. This scopes the request rather than authenticating it, and it is required on every operation marked x-mixpeek-namespace-scoped.

Path Parameters

session_id · string · required

Session ID

confirmation_id · string · required

Confirmation ID

Body

application/json

Request to approve or deny a pending confirmation.

approved · boolean · required

True to approve, False to deny the action

Response

200

application/json

Successful Response