All v2 error responses use the same response envelope as success responses. This makes error handling consistent and predictable.Documentation Index
Fetch the complete documentation index at: https://docs.humandesignapi.nl/llms.txt
Use this file to discover all available pages before exploring further.
Basic Pattern
- Check
success— iffalse, the request failed - Read
errorCode— use this for programmatic logic - Never parse
message— it is human-readable and may change without notice
HTTP Status Categories
| Status | Meaning | Retry? |
|---|---|---|
| 400 | Validation error (bad input) | No — fix the request |
| 401 | Authentication failure | No — check your API key |
| 402 | Credits exhausted | No — wait for reset, enable overage, or upgrade |
| 403 | Access denied (wrong tier or inactive) | No — upgrade plan or contact support |
| 429 | Rate limit exceeded | Yes — wait for Retry-After seconds |
| 500 | Server error | Yes — retry with backoff, contact support if persistent |
Retry Strategy
- Only retry
429and500errors - Never retry
400,401,402, or403— these require a change in the request or account - For
429, use theRetry-Afterresponse header (value in seconds) - For
500, use exponential backoff (1s, 2s, 4s, max 3 retries)

