Rate limits - TrendlineLabs API

Each key may make limit requests per window_s seconds. GET /public/v1/key returns both for the calling key: that answer is the truth, whatever this page says. Access is free, and every granted account is on one plan: 60 requests per 60 seconds per key.

Headers

Once your key has passed the limiter, every answer carries:

header	meaning
`X-RateLimit-Limit`	requests allowed per window
`X-RateLimit-Remaining`	requests left in this window
`X-RateLimit-Reset`	seconds until the window resets

They are present on a 200 and on the enveloped refusals that come after the limiter: 404, 409, 410, 422, 429, 500 and 503. They are absent on refusals that come before it (401, 403, the failed- authentication 429, and a 503 or 500 raised while the key itself is being checked), and on a text/plain 500.

When you are limited

A 429 rate_limited carries Retry-After: wait that many seconds. Two limits answer 429:

your key’s own window (with the X-RateLimit-* headers);
failed authentications from one address (without them).

Some 503s also carry Retry-After: candles while the history source is busy, and the account routes’ venue_unavailable and venue_busy.