Limits and throughput

​

Before you start

• Choose one venue and market type, symbol, data family, and time window.
• Read Rate limits for your plan’s capacity and Errors for retry behavior.
• Set a worker count, page budget, retry budget, and output path before the first request.
• Keep the API key in the runtime environment and out of job logs.

​

Inputs

​

Steps

END=$(( ($(date +%s) - 3600) * 1000 ))   # one hour ago, in Unix milliseconds
START=$(( END - 3600 * 1000 ))           # one hour earlier

curl -sS "https://api.0xarchive.io/v1/hyperliquid/trades/BTC?start=$START&end=$END&limit=100" \
  -H "X-API-Key: $OXARCHIVE_API_KEY"

​

What a finished run looks like

​

If something fails

• 400, invalid symbols, or invalid parameters: fix the input before another call.
• 401: repair the key source or X-API-Key header.
• 403: read the exact error for that endpoint, account, and key, and stop unchanged retries.
• 429: retry rate_limited within the budget and stop on insufficient_credits, as When you reach a limit describes.
• 5xx or timeout: retry within budget, then check Data quality and stop if the budget is exhausted.
• Page budget reached with a cursor remaining: mark the output partial and resume from the saved cursor under a new bounded run.
• A stale or incomplete quality result: narrow, delay, or mark the output as described in gap handling.

​

Saved run metadata

{
  "run": "btc-trades-throughput-001",
  "venue_family": "hyperliquid_core",
  "symbol": "BTC",
  "data_family": "trades",
  "route": "/v1/hyperliquid/trades/BTC",
  "query": {
    "start": "START in Unix ms",
    "end": "END in Unix ms",
    "limit": 100
  },
  "workers": 1,
  "page_budget": "record the finite page count",
  "retry_budget": "record the finite attempt count",
  "request_ids": ["00000000-0000-0000-0000-000000000000"],
  "output": "./artifacts/btc-trades-throughput-001.json",
  "stop_reason": "record the observed completion or stop reason"
}

​

Next step