All SDK errors derive fromDocumentation Index
Fetch the complete documentation index at: https://docs.minerva.io/llms.txt
Use this file to discover all available pages before exploring further.
MinervaError. The hierarchy lets you catch
broadly (any SDK error) or narrowly (specific failure mode), and most carry
context attributes so you can build a useful UI without parsing message
strings.
The hierarchy
Quick reference
| Exception | When | Carries |
|---|---|---|
MinervaValidationError | Bad input — raised locally, before the call | — |
MinervaAuthError | 401/403 — invalid key or not entitled to this endpoint | — |
MinervaRateLimitError | 429 — back off and retry | .retry_after (seconds) |
MinervaAPIError | Other 4xx/5xx | .status_code, .api_request_id, .body |
MinervaConfigError | Misconfiguration | — |
Rate limits
retry_after is the server’s hint in seconds. Fall back to a sane default
(1s) if the server didn’t supply one.
Server errors
api_request_id is the server’s trace ID — quote it when reporting issues to
support. Responses are forward-compatible: fields the server adds later won’t
break an older SDK.
Validation errors
MinervaValidationError is raised locally before any HTTP call — bad
payload shape, over-the-limit record counts, missing required fields:
dry_run=True to trigger the same validation without committing to the
call — see Validation & dry_run.
Catch-all
MinervaAuthError is also raised when no MINERVA_API_KEY is set (or
api_key= passed) — that’s a local check, before any HTTP call. The error
message tells you exactly what’s missing.
