code field of an error response, what they mean, and how to resolve them.
| Code | Meaning | Scope | What to do |
|---|---|---|---|
advanced_tier_required | The endpoint needs the Advanced tier | Plan | Upgrade to Advanced |
futures_access_required | Futures access is not on this key | Plan | Advanced tier, or the futures data add-on |
*_scope_required | Behind an exchange data license we are finalizing | Global | Not a purchase; access returns once the license is in place |
historic_data_access_missing | Requested date is older than your plan’s lookback | Plan | Use a more recent date, or the Data Shop for older history |
historical_data_not_supported | Endpoint serves the latest trading day only | Endpoint | Use the full-tape or history endpoint for older data |
daily_request_limit_hit | The token used up its request cap | Plan | Wait for the cap to reset, or upgrade |
concurrent_limit_exceeded | Too many of your requests were in flight at once | Request | Keep at most current_limit requests in flight and retry after a short backoff with jitter. See Rate limits |
401 | No token reached us | Request | Send Authorization: Bearer YOUR_API_KEY; the key itself is usually fine |
404 | Route does not exist | Request | Check the path against the endpoint list; guessed route names 404 |