API Rate Limits

Current defaults

For Option Chain, keep sustained traffic at one request per second per customer and short bursts to 10 requests or fewer, for example when fetching several expirations. Apply this guidance across all of your API keys and IP addresses. Current throttling is best-effort; this is client usage guidance, not a guaranteed global quota. HTTP 429 includes a Retry-After header. Historical SQL and the other HTTP surfaces retain their documented best-effort endpoint limits.

The planned limits below are not yet active. No effective date has been announced. The current defaults remain in effect until enforcement is rolled out and announced.

Planned trial and paid limits

These are requests per customer, separately for each endpoint. Both the minute and hourly limits apply once enabled; reaching either limit triggers rate limiting.

• All API keys and IP addresses belonging to the same customer will share each future endpoint quota. Rotating keys or changing IP addresses will not create a new allowance.
• The three endpoints will have separate quotas, not one combined request pool.
• Enterprise limits are contract-specific. Contact Sales or Support at support@optiondata.io for higher-volume access.
• This planned rate policy does not change prices, subscription access, response row caps, or data freshness.

Handling a rate-limit response

HTTP 429 means a rate or connection limit was reached. Honor the Retry-After response header before retrying, and use backoff instead of sending an immediate retry loop.

For Option Chain, the latest session updates about every 90 seconds during market hours. Poll no more often than every one to two minutes and compare meta.as_of before doing new work. The sustained-rate and burst guidance accommodates interactive or multi-filter requests; it is not a recommendation to poll at that rate.

Realtime WebSocket is separate

Realtime WebSocket remains limited to 5 concurrent connections per API token. HTTP request quotas do not apply to streamed trade messages. Existing connection behavior is unchanged.

中文：当前默认与计划限额

期权链建议按客户将持续请求速率控制在每秒 1 个请求以内，短时并发请求控制在 10 个以内，例如同时获取多个到期日。同一客户的所有 API 密钥和 IP 地址应合计遵守这一建议。当前限流属于尽力保护；这些是客户端使用建议，不是保证严格执行的全局配额。触发限制时返回 HTTP 429，并附带 Retry-After 响应头。历史 SQL 和其他 HTTP 接口继续使用各自文档中的尽力限额。

下表是计划限额，尚未生效。生效日期尚未公布；在限流部署并公告前，继续适用当前默认值。

启用后，每分钟与每小时限额将同时适用，按客户、按端点分别计算；任一限额用尽即触发限流。同一客户的所有 API 密钥和 IP 地址将共用该端点的额度，更换密钥或 IP 不会增加额度。三个端点不是共用一个请求池。

企业限额按合同约定；如需更高调用量，请联系销售或客服 support@optiondata.io。此计划不改变价格、订阅权益、响应行数上限或数据时效。

收到 HTTP 429 时，请等待 Retry-After 指定的时间后重试，并采用退避机制。交易时段内期权链最新交易日约每 90 秒更新一次，建议轮询间隔不短于 1–2 分钟，并在处理前比较 meta.as_of。持续速率和短时并发建议用于交互查询或多筛选请求，不是建议轮询频率。

实时 WebSocket 保持每个 API token 最多 5 条并发连接；HTTP 请求配额不适用于推送消息。