Status codes
Use the HTTP status and the stable error code to decide whether to correct the request, check access or retry later.
HTTP status and error codes
API errors use application/problem+json with type, title, status, detail and code. Some requests may receive a 429 response before reaching the API, with a different body format. Check Content-Type before interpreting the response and respect Retry-After when present.
| Status and code | What to do |
|---|---|
400 INVALID_PARAMETERS | Correct the unknown, repeated or out-of-range parameter. |
401 UNAUTHORIZED | The key is missing or invalid. |
403 ACCESS_DENIED | The key is not enabled; contact help@ledgifi.com. |
404 NOT_FOUND | Check the RUN, series code or download file id. |
200 · history.unavailableReason=HISTORY_NOT_PUBLISHED | The detail is available, but history.points is null because verifiable published history is unavailable. Published history with no observations returns an empty list instead. |
429 QUOTA_EXCEEDED | Wait for the number of seconds in Retry-After; quotas use one-minute and 30-day windows. |
503 SERVICE_UNAVAILABLE | Try again later. |