API · GET
GET /v1/approvals
List pending approvals — filterable by approver, agent, or risk class.
Overview
GET /v1/approvals
Returns approvals routed to the requesting user. Supports filtering by approver, agent, workflow, status, risk class or SLA window. Used by approval UIs and SLA-monitoring tools.
All xyner API calls require an OAuth2 bearer token with the appropriate scope. Every request is identity-bound and audit-captured.
Request
Example request
curl -X GET \
-H "Authorization: Bearer $XYNER_TOKEN" \
'https://api.xyner.ai/v1/approvals?approver=me&status=pending&risk=high'
Response
Example response
A successful response has shape:
{
"approvals": [
{
"id": "apr_01H8Z",
"agent": "claims-triage-agent",
"workflow_id": "wf_01H8Z",
"action": "approve_payout",
"amount": 12500.00,
"rationale": "Coverage confirmed; fraud score 0.18; precedent claim CLM-298440 paid.",
"sla_deadline": "2026-04-12T11:00:00Z",
"decision_url": "/v1/approvals/apr_01H8Z/decide"
}
]
}
Notes
Things worth knowing
Useful behavioural details for this endpoint.
- All endpoints support OpenTelemetry trace-context propagation via standard W3C headers.
- Idempotency keys are honoured for 24 hours (or longer for endpoints that explicitly support extended idempotency).
- Errors follow RFC 7807 problem+json with a stable error code in
type. - Every successful action produces one or more audit records, queryable via /v1/audit/query.
- Rate limits apply per-tenant; current limits are returned in
X-RateLimit-*response headers.
See also
Related endpoints and concepts
This endpoint is part of the broader xyner platform API. For an end-to-end view, see the platform overview and the documentation hub.
Get started
Ready to put autonomous agents to work?
See xyner in your environment with a guided executive demo.