Skip to main content
Perps REST endpoints share your key’s standard /v3 rate limit — there is no separate perps quota to think about. Every response carries x-ratelimit-limit, x-ratelimit-remaining, and x-ratelimit-reset headers.

​
WebSocket limits

Concurrent connections to wss://perps.polynode.dev/ws per key: One connection can carry all your channels — the subscription cap is what matters, and a single subscription like perps_tickers covers every instrument at once. These are the plan defaults; individual keys can carry a custom allowance. The hello frame you receive on connect reports your key’s exact max_subscriptions — treat that as authoritative.

​
Practical notes

  • If you find yourself polling market data faster than about once a second, the WebSocket will serve you better — it pushes every update as it happens.
  • Wallet portfolio data refreshes every few seconds; querying the same wallet faster than that returns the same snapshot.
  • Historical endpoints (/oi, /volume, time-windowed /trades) paginate with limit + more; prefer larger pages over many small ones.