Error codes
The API uses standard HTTP status codes. An error body carries the service's detail JSON object, with the exact message returned to the caller.
Error structure
{ "detail": "<message>" }An authentication refusal also carries the WWW-Authenticate: ApiKey header; a script client refused for a missing key additionally gets a docs link to the quickstart.
Common codes
| Status | Returned body | Suggested action |
|---|---|---|
| 400 | Invalid timeframe. Valid: … | Fix the query parameters. |
| 401 | API key required | Send the key as X-API-Key or Authorization: Bearer. |
| 401 | Invalid or expired API key | Check the key, rotate it if it was revoked. |
| 401 | Authentication required | Protected route: provide a valid key. |
| 403 | Upgrade required | The metric or route is above the account plan. |
| 404 | Not Found, Indicator not found, Unknown metric | Check the path and the identifier (indicator, metric). |
| 429 | Rate limit exceeded / Daily quota exceeded | Honor Retry-After (60 s per key, 86400 s for the anonymous quota). |
| 5xx | Generic service response. | Retry with back-off ; contact support if persistent. |
Institutional disclaimer
Trinity Insights is an educational and analytical tool. Content does not constitute investment advice. Trinity Insights is not a Crypto-Asset Service Provider (CASP) registered under MiCA Regulation (EU) 2023/1114, nor a Financial Investment Advisor (CIF), nor a PSAN. See the full disclaimer.