2 min read
Endpoint
| Method | GET |
| Path | /partner/v1/* |
| Ring | partner (error model) |
Parameters
Not applicable — this page documents the shared error shape returned across the partner ring.
Response
| Status | Code family | Meaning | Retry? |
|---|---|---|---|
| 400 / 422 | bad_request / validation | Malformed or invalid body | No |
| 401 | invalid_token | Missing / expired / bad token | Re-mint once, then yes |
| 403 | insufficient_scope | Token lacks the scope | No — fix the credential |
| 404 | not_found | Unknown resource | No |
| 409 | conflict | Duplicate / state conflict | No — reconcile |
| 429 | rate_limited | Bucket empty (see RateLimit-*) | Yes — after Reset |
| 5xx | server_error | Transient fault | Yes — back off |
Errors
OAuth errors on the token plane follow the OAuth spec (invalid_client, invalid_scope). Pair retries with an idempotency key on writes so a replay never double-acts.
Frequently asked questions
How should I handle a 401?
Distinguish expired from invalid. If the token merely expired, mint a fresh one and retry the request once. If the credential is bad or revoked, re-minting will also fail — fix the credential rather than looping.
Is a 409 retryable?
No. A 409 is a conflict — often a duplicate created without an idempotency key, or a state clash. Reconcile the underlying state (or send the correct idempotency key) before resubmitting.
Related reading
Funding for UK limited companies
Credit Corp lends to your company, not to you personally — short-term working capital with no personal guarantee. See what your business could access.