Per-minute rate limit
Most requests count as one unit against a rolling 60-second window with the exception of/api/v1/*_search endpoints, which consume quota dynamically based on the limit and full_reference_data parameters. Your tier’s exact limit is reported on every response in the ratelimit header, which is the source of truth.
Response headers
We follow the IETF draft v7 RateLimit header fields:
Example:
When you exceed the limit
You’ll get429 Too Many Requests with retry-after set. The body uses the standard error envelope:
reset (or retry-after) has elapsed and retry. If the server is shedding load, you may also see 429 briefly while it recovers.
Practical tips
- Read the
ratelimitheader and slow down before you hit zero. - Batch ISINs into one call when you can. Every endpoint accepts a list.
- Add jitter to your retries to avoid thundering-herd patterns.
Monthly ISIN quota
Your tier caps how many distinct ISINs you can pull reference, pricing, or cash flow data for in a billing month. After an ISIN counts against your quota in a given month, repeated requests for it that month are free.Tiers
Allowances, price-history windows, and resource access depend on your plan. Common tiers:- Startup:
- 3,000 ISINs returned / month on reference, pricing, cashflows and equivalent endpoints;
- 10,000 ISINs returned / month on search endpoints;
- 1-year price history.
- Enterprise: custom allowances and price-history windows.
