Revenue
Get production vs shadow routing comparison
Read-only comparison between persisted production routing and shadow strategy. When ROUTING_ENGINE_V2_ENABLED=true, shadow runs the full orchestrator pipeline in SHADOW mode with fixture delivery (no dial / no live egress). Optional policyId query overrides the shadow policy. Disabled unless SHADOW_ROUTING_ENABLED=true.
https://api.thearvexa.com/api/calls/{id}/shadow-routingCalls
Recent Requests
Log in to see full request history| Time | Status | User Agent |
|---|---|---|
| Make a request to see history. | ||
Path Params
idstringrequiredQuery Params
policyIdstringrequiredHeaders
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
200Shadow routing comparison
Shadow routing comparison
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.