Core Comparison Dimensions
| Dimension | Key Evaluation Question | Technical & Architectural Impact |
|---|---|---|
| Request Frequency | How many REST calls per second or minute does your system need? | Excess requests trigger rate limits; high-frequency needs token-bucket or cache layer |
| Subscribed Symbols | How many tickers must stream simultaneously over WebSocket? | Affects connection bandwidth; for large universes use centralized pub/sub broadcast |
| Connection Concurrency | Do multiple distributed processes or worker nodes connect at once? | Cluster or HA deployments must account for concurrent socket connection quotas |
| Historical Depth | How far back do your backtests reach? Any bar count limits on equities? | Lookback varies by asset; /kline caps each request at 500 bars and stock timestamp cursors are unsupported |
| Market Entitlements | Are all required markets (HK, US, A-Shares, FX, metals) included? | Ensure selected tier encompasses all targets; full-market access may require enterprise tier |
| Usage Purpose | Internal quantitative research or client-facing redistribution? | Commercial applications showing data to external users require redistribution agreements |
Scenario-Based Sizing Estimates
Free trial quotas are generally sufficient for validating schemas, field definitions, and Python/WebSocket scripts at zero cost.
Focus on symbol capacity and WebSocket resilience. A single socket can subscribe to multiple symbols and broadcast internally.
Verify historical lookback depth for required asset classes. Fetch data asynchronously after hours and store in a time-series database.
For public-facing market dashboards or multi-tenant apps, contact AllTick to arrange licensing scope, compliance terms, and dedicated SLA.
Common Misconceptions to Avoid
Tier specifications define tiered historical depths for different asset classes. Equities often carry limits on recent bars. Do not assume maximum lookback for one asset applies across all instruments. /kline returns a maximum of 500 bars per request; timestamp pagination supports FX, metals, and crypto, not stock codes.
Debugging Rate Limit Errors
Exceeding allocated rate limits will return HTTP 429 status codes. See our troubleshooting guide for mitigation strategies.