Rate limits & idempotency

Per-key and per-IP rate limits with Retry-After, plus idempotent writes: Idempotency-Key for orders and deposits, X-Request-Id for scraper calls.

Requests are rate limited per key and per IP; exceed it and you get a 429 with a Retry-After header. Back off and retry. Scraper calls allow bursts of 100 with a sustained 20 requests per second per account.

Idempotency

For any write (POST /orders, POST /deposits) send an Idempotency-Key header with any unique string you choose. A retry with the same key converges on the same order instead of creating a second one, so a dropped connection never double-charges.

Idempotent order

curl -X POST https://hproxy.com/api/v1/orders \
  -H "X-API-Key: hpx_your_key_here" \
  -H "Idempotency-Key: your-unique-id-123" \
  -H "Content-Type: application/json" \
  -d '{"product_id":"residential-lite","quantity":5}'

Scraper calls have the same protection under their own X-Request-Id header: a retry with the same value replays the original result and is never billed twice. See Run a scraper.

← Previous

Authentication

Errors

Need a hand wiring this up? Email [email protected]. A real person reads every message.