Reference
Confirmations
Human-in-the-loop confirmation listing and decision endpoints.
Endpoint Map
| Method | Path | Auth | Purpose |
|---|---|---|---|
GET | /api/v1/confirmation/list | Flexible auth | List DB confirmations (status filter supported) |
GET | /api/v1/confirmation/pending | Flexible auth | List in-memory pending confirmations |
GET | /api/v1/confirmation/:id | Flexible auth | Get one confirmation by request ID |
POST | /api/v1/confirmation/:id/respond | Flexible auth | Confirm/reject with optional reason |
POST | /api/v1/confirmation/:id/confirm | Flexible auth | Confirm shortcut |
POST | /api/v1/confirmation/:id/reject | Flexible auth | Reject shortcut |
List Confirmations
GET /api/v1/confirmation/list?status=pending
Authorization: Bearer <jwt>status supports: pending, confirmed, rejected, expired, consumed.
Respond
POST /api/v1/confirmation/:id/respond
Authorization: Bearer <jwt>
Content-Type: application/json
{
"confirmed": true,
"reason": "Looks good"
}If confirmed, response may include short-lived confirmation_token and expiresIn seconds.
Shortcuts
POST /api/v1/confirmation/:id/confirm
POST /api/v1/confirmation/:id/rejectNotes
- Access is restricted to the initiating user/end-user, or tenant admin with admin role.
- Timeout is recorded as a rejection with reason
Request timed out.