Errors and retries
Problem details, auth failures, not founds, and rate-limit handling
AskElephant’s public API uses application/problem+json for error responses.
Error shape
Core fields
Common statuses in the live API
Retry guidance
- Retry
429only after respectingRetry-After. - Do not retry
401until you refresh or replace the credential. - Do not retry
403until the credential has the required scope. - Do not retry
404unless the resource may legitimately appear later.
Support tip
Include request_id when reporting issues to AskElephant so requests can be traced quickly.