Rate limits

API-key traffic is rate-limited per key.

1,200 requests / 60 seconds

A rolling 60-second window. Your current budget is reported on GET /api/v1/me under rateLimit.

When you exceed the limit, requests return:

429 Too Many Requests

Staying under the limit

Stream instead of poll

For live prices and chat, use WebSockets. One subscription replaces a tight polling loop and doesn’t consume your REST budget.

Batch your reads

GET /api/v1/positions returns perps + spot + predictions in one call; GET /api/v1/groups/{id}/proposals returns spot + prediction proposals together. Prefer the aggregate over per-vertical loops.

Back off on 429

Use exponential backoff with jitter. Don’t hammer — repeated 429s waste the window.

Backoff example

async function withRetry(fn, { tries = 5 } = {}) {
  for (let i = 0; i < tries; i++) {
    const res = await fn();
    if (res.status !== 429) return res;
    const wait = Math.min(2 ** i * 250, 8000) + Math.random() * 250;
    await new Promise(r => setTimeout(r, wait));
  }
  throw new Error("rate limited: gave up after retries");
}

import random, time

def with_retry(fn, tries=5):
    for i in range(tries):
        res = fn()
        if res.status_code != 429:
            return res
        time.sleep(min(2 ** i * 0.25, 8) + random.random() * 0.25)
    raise RuntimeError("rate limited: gave up after retries")

Get started

Example flows

Core concepts

Trading guides

Real-time (WebSockets)

1,200 requests / 60 seconds

Staying under the limit

Backoff example

1,200 requests / 60 seconds

​Staying under the limit

​Backoff example

Staying under the limit

Backoff example