Docs · API
Everything the interface can do, your systems can do too.
The Adanse API is workspace-scoped and governed by the same policies as the product. Calls made with a key produce identical decision records and audit evidence.
Authentication
Workspace API keys
curl https://adanse.ai/api/public/v1/decisions?status=pending \ -H "Authorization: Bearer $ADANSE_API_KEY"
Keys are created in the workspace, hashed at rest and shown once. A key inherits the authority of the role that issued it: read keys can query, decider keys can approve, reject and undo. Every call is attributed in the audit trail with the key that made it.
Endpoints
Core resources
GET/v1/decisions
List decision records. Filter with ?status=pending|approved|rejected.
GET/v1/decisions/{reference}
One decision with reasoning, inputs, applied policy and audit links.
POST/v1/decisions/{reference}/decide
Approve or reject a pending decision. Requires a decider key.
GET/v1/employees
AI employees with department, remit, autonomy ceiling and state.
GET/v1/memory
Business Memory entries by type, entity, source and freshness.
GET/v1/audit
Append-only audit events, newest first, linked to their decision.
Response
A decision record, in JSON
{
"reference": "DR-2148",
"title": "Hold payment batch PB-771 pending bank-detail check",
"status": "pending",
"risk": "R3",
"employee": { "name": "Collections Analyst", "department": "Finance" },
"reasoning": "Supplier bank details changed 6 days ago...",
"policy": { "name": "Payment release control", "version": 4 },
"value": { "currency": "USD", "amount": 42150 },
"created_at": "2026-09-01T08:14:22Z"
}Errors and limits
Predictable failure
401
No valid key, or the key has been revoked.
403
Authenticated, but the key lacks authority for this action.
409
The decision has already been resolved by another approver.
422
Policy blocked the action; the response names the policy that applied.
429
Rate limit reached. Read keys allow 600 requests per minute per workspace.