Rates and quotas
Subscription usage is counted per user across all connections in one pool. Account quote entitlements determine the total. Do not infer this service’s limits from other products’ tables.
Accounting
- quote, order_book and ticker for the same instrument are separate subscription keys.
- kline consumes quota, with a key including instrument, period and adjust.
- Identical keys are deduplicated across sessions. A slot is released after no sessions reference it. Derived depth data does not consume another slot.
- Options use concrete subscription keys in the same pool as equities. They are not grouped by option chain and have no separate option-subscription quota.
- Standard and option-chain historical pools are independent of subscriptions; see market data permissions and quotas.
For example, two connections of the same user subscribing to US.AAPL quote consume one slot. Adding ticker or K-lines with different periods or adjustments adds usage.
Quota and rate errors
A subscription that would exceed quota can return business code=4:
{"id":"sub-001","code":4,"message":"sub quota exceeded, max=..."}Reduce subscriptions or wait for quota changes before retrying. Do not retry continuously. Subscribe/unsubscribe control requests are also subject to current business rate policies; see rate limits.
Release and reconnect
Unsubscribe from unneeded data promptly. A key still referenced by another connection continues to consume account quota. Session cleanup after an abnormal disconnect can be delayed; immediate release is not guaranteed. Reconnect, authenticate and restore subscriptions using a new session.
Depth and display
Quota does not grant quote permissions. Order-book depth, broker queues and instrument access remain subject to market entitlements. Render the fields and array lengths actually received. Process ticker_list as an array: one message may carry multiple trades. Batch subscriptions and use reconnect backoff to avoid rapid subscription churn.