Errors¶
Spendware APIs use HTTP status codes plus JSON response bodies. SDKs translate many API failures into typed management errors.
| Status | Meaning | Typical Fix |
|---|---|---|
400 |
Domain validation failed. | Fix payload values or workflow state. |
401 |
Missing or invalid credential. | Check key, token, and base URL. |
403 |
Scope or RBAC denied. | Add scope or grant resource access. |
404 |
Resource is missing or not visible. | Check ID, organization, and access. |
409 |
Conflict. | Check duplicate resources or idempotency mismatch. |
422 |
Request schema validation failed. | Match OpenAPI schema. |
429 |
Rate limit exceeded. | Back off and retry. |
5xx |
Server failure. | Retry with idempotency where safe and capture request ID. |
SDK Handling¶
Python SDK exceptions live under spendware_provider_sdk.management.errors. TypeScript SDK errors are exported from @spendware/provider-adapters-sdk/management.
Capture status code, error code, detail, and request ID when reporting issues.