Reference
Errors
Errors use standard HTTP status codes and an application/problem+json body (RFC 9457) with a stable code you can switch on.
Error format
typeA link to the code on this page.titleShort, human-readable summary.statusThe HTTP status, repeated in the body.codeStable machine-readable code. Switch on this, not on title or detail.detailWhat went wrong in this request, when there is more to say.positionFor invalid_query: character offset of the problem in q.request_idAlso in the X-Request-Id header. Quote it when you contact support.
Codes
A parameter or body field is missing, has the wrong type or is out of range.
Read detail; it names the field.
The text query does not parse, or names an unknown field or operator.
position is the character offset of the problem in q.
No key, a malformed key or a revoked key.
Send Authorization: Bearer ys_live_… with an active key.
The account behind the key has no paid plan, or the plan has ended.
Renew the plan in Billing. Keys keep working once it is active.
The key lacks the scope, or the resource belongs to another account.
Create a key with the scope the endpoint lists.
No object with that id, or no screen or report on that date.
Check the id prefix and the date format (YYYY-MM-DD).
The account already has the maximum number of keys (5), saved queries (50), watchlists (50) or watched wallets (10).
Delete one first.
More than 60 requests in a minute or 5,000 in a day on this key.
Wait Retry-After seconds. Cache responses: data changes once a day.
Something failed on our side.
Retry with backoff. Send request_id to support if it persists.