Every error from the Nubo API follows the same shape:Documentation Index
Fetch the complete documentation index at: https://docs.withnubo.com/llms.txt
Use this file to discover all available pages before exploring further.
- The HTTP status tells you the broad category (4xx client error, 5xx server error).
internal_codeidentifies the specific failure and is stable over time.messageis a human-readable description. The text may be reworded between releases; your client should not pattern-match on it.
Using codes in your client
- Branch on
internal_codeonly when you need to react to a specific failure (e.g. distinguishing “rate limited” from “invalid token”). - Use the HTTP status for everything else.
- Treat unknown codes as the generic category implied by the HTTP status - new codes are added as we add new behavior.
- Retry
5xxand429with a short backoff. Don’t retry4xx.
API version header
internal_code | HTTP | Cause |
|---|---|---|
V-Tn4qZ8 | 400 | Nubo-Version header isn’t an ISO-8601 date (YYYY-MM-DD). |
V-Kp7mR2 | 400 | Date is well-formed but not a supported version. |
Stability
Per our stability policy, the error envelope won’t change for a pinnedNubo-Version. New codes may be added at any time, but existing codes keep their meaning.