Support
For onboarding, billing, or technical questions, reach us through the channels below.
Technical and account issues are prioritized on business days
Developer FAQ
Common questions when integrating market data APIs.
Which markets and data types does TIQEX support?
US, CN, HK equities, forex, crypto, futures, indices, and commodities. REST for snapshots and history; WebSocket for live streams.
How does authentication work? Can I put keys in the browser?
Send X-API-Key on every request. Store keys server-side only—never in public frontend bundles.
What can the free tier do? When should I upgrade?
Free tier is for learning and integration tests. Upgrade for WebSocket, lower latency, higher quotas, or more markets in production.
How should I handle HTTP 429 rate limits?
Honor Retry-After, use exponential backoff, log X-Request-Id for support, and cache non-real-time data locally.
Where are error codes documented?
Failures return succ=false with msg and code. Use the X-Request-Id response header for tracing. Common quota codes: DAILY_LIMIT_EXCEEDED / RATE_LIMIT_EXCEEDED.
How should REST and WebSocket work together?
Use REST for snapshots and historical candles; WebSocket for live ticks. Same API key. Stream handshake counts once; pushed ticks are not re-billed.
How do I format symbols?
Crypto often uses BTCUSDT; US equities like AAPL; multi-market quote accepts product short codes or TV symbols. See each endpoint’s parameter table and the console symbol lists.
How should I interpret latency and coverage?
Latency, field granularity, and history depth vary by market and plan—check console entitlements and endpoint docs. Output may not match any single exchange tick-for-tick.
Contact channels
Pick the option that fits best. For urgent production issues, email us with your account and request ID.
Email support
Write to [email protected] and we will get back to you.
Send emailTelegram
Follow the channel or message support for updates and help.
Open TelegramDeveloper docs
Quickstart, auth, REST, and WebSocket guides.
Read docsResponse notes
On business days we prioritize production outages and auth issues. General questions are usually answered within 1–2 business days.