Revenue
Get call settlement explainability
Returns tenant-scoped settlement inspection for a call: M8 duration qualification gate, optional M9 CallQualification enrichment (callQualification), Charge, Payout, Ledger lines, adjustments, pricing sources, and a deterministic explainability summary. Explicitly separates settled charge (from pricing resolution) from routing bid evidence (never billing truth). Bids are never qualification truth. Monetary amounts are returned only for SUPER_ADMIN and ORG_ADMIN. Read-only — never writes finance rows.
https://api.thearvexa.com/api/calls/{id}/settlementCalls
Recent Requests
Log in to see full request history| Time | Status | User Agent |
|---|---|---|
| Make a request to see history. | ||
Path Params
idstringrequiredHeaders
x-organization-idstringrequiredTenant organization identifier
x-user-rolestringrequiredDevelopment RBAC role (for example SUPER_ADMIN, ORG_ADMIN, OPS_MANAGER, VIEWER)
x-user-idstringTrusted authenticated actor id (interim header auth). Recorded as the actor on sensitive writes such as finance adjustments and their approve/reject decisions. Ignored when header auth is disabled.
x-organization-idstringrequiredx-user-rolestringrequiredResponses
200Call settlement explainability
Call settlement explainability
No response body schema in OpenAPI
This status is documented, but the operation did not publish a response schema or example. The HTTP status and description above are still authoritative.
400Validation error
Validation error
No response body schema in OpenAPI
This status is documented, but the operation did not publish a response schema or example. The HTTP status and description above are still authoritative.
403Forbidden for the supplied role
Forbidden for the supplied role
No response body schema in OpenAPI
This status is documented, but the operation did not publish a response schema or example. The HTTP status and description above are still authoritative.
404Resource not found
Resource not found
No response body schema in OpenAPI
This status is documented, but the operation did not publish a response schema or example. The HTTP status and description above are still authoritative.