Glossary

WebSocket vs REST Polling

Channel choice affects latency, bandwidth and complexity — not just subscription price.

REST polling

Periodic HTTP requests for snapshots. Simple but latency-bound by poll interval; easy to hit rate limits at high frequency.

WebSocket push

Server pushes after a persistent connection. Great for dashboards and alerts — implement reconnect and heartbeats.

Recommended pattern

REST for bootstrap and history; WebSocket for live state. One TIQEX API key covers both.

Limit budgets

REST polling burns RPM/daily caps; WS is constrained by subscriptions/messages. Budget channels separately.

Practice

Reconnect + Node guides; auth failures → /docs/auth.