Errors
Handle the actual interface envelope and credential-failure semantics.
Standard /v1 uses protocol-native errors. Existing open edges, Java funding and console queries retain their business envelopes. Keep request identifiers, HTTP status and machine codes without logging plaintext Keys.
- 401/403: invalid, revoked or insufficient-scope credentials cannot retry into stronger privileges. Restore an expired session through its login journey while preserving the order.
- 503: retry dependency failures according to applicable Retry-After; never render zero funds or an empty catalog.
- 409: the same idempotency key with a different payload or contract is a conflict without side effects. Do not bypass it with a random new key.
- Transport timeout: execution may have occurred. Query the original task/order or billing state first.
SDK HTTPError, NetworkError, BusinessError and CompliancePollError classify layers. POST is not automatically replayed by default; compliance writes do not replay after 401. Missing final usage means pending reconciliation, not free execution.