Credits and limits
Every REST API request spends credits from your plan. Credits are the API’s only rate limit.
How credits are counted
Section titled “How credits are counted”- Two rolling windows. Your plan gives you an allowance for the last 24 hours and another for the last 30 days. A request is refused if either window has too few credits left. There is no reset time: credits come back as old requests leave the window.
- Checked before, charged after. A request is checked against what it could cost, then charged for what it returns. A request that returns less data costs less, and a request that fails is not charged.
- Your allowance comes from your plan. See Plans and credits.
- See your usage in API Access in your account settings.
When a window runs out, requests get 429 until credits free up. See Errors.
What each request costs
Section titled “What each request costs”| Request | Credits |
|---|---|
| List instruments, list currencies | 1 |
| List top currencies | 1 per currency requested |
| Get currency rates | 1 per quote currency returned |
| Historical bars, prices or currency rates | 1 per 1,000 bars returned |
| Historical ticks | 1 per 12 hours requested |
The REST API reference states the cost on every endpoint.
Limits on one request
Section titled “Limits on one request”- Bars: at most 2,500 per request. A longer range is cut to the 2,500 bars that end at
end. To fetch more, page backwards: make the next request’sendthe first bar’s time. - Ticks: at most 1 day per request.
- Intervals: sub-minute bars (
S5,S15,S30) are not available. Currency history has no ticks. - History start: if
startis before the first price held, the bars start at the first price held. Check the first bar’s time.