Rate Limits

​

Overview

​

Default limits

​

Rate limit headers

​

Handling rate limits

HTTP/2 429
X-RateLimit-Limit: 300
X-RateLimit-Remaining: 0
X-RateLimit-Reset: 1716422460
Retry-After: 12
Content-Type: application/json

{
  "error": "rate_limit_exceeded",
  "code": "rate_limit_exceeded",
  "type": "rate_limit",
  "hint": "Rate limit exceeded. Retry after 12 seconds.",
  "request_id": "req_01H..."
}

​

SDK auto-retry

const arcus = new Arcus({
  apiKey: process.env.ARCUS_API_KEY,
  entityId: process.env.ARCUS_ENTITY_ID,
  maxRetries: 3,   // default: 2
  timeout: 30000,  // ms; default: 30000
});
// SDK automatically waits Retry-After seconds before retrying 429s

arcus = Arcus(
    api_key=os.environ['ARCUS_API_KEY'],
    entity_id=os.environ['ARCUS_ENTITY_ID'],
    max_retries=3,   # default: 2
    timeout=30,      # seconds; default: 30
)

client := arcus.NewClient(
    os.Getenv("ARCUS_API_KEY"),
    arcus.WithEntityID(os.Getenv("ARCUS_ENTITY_ID")),
    arcus.WithMaxRetries(3),
    arcus.WithTimeout(30 * time.Second),
)

​

Best practices for high-volume integrations

1. Bulk endpoints: prefer batch operations (e.g. bulk product import) over individual creates in a loop
2. Pagination: use limit=100 to minimize list requests
3. Concurrency: keep concurrent requests below 10 per key; spread load across multiple keys if needed
4. Backpressure: implement exponential backoff even for retries that are not rate-limit-related
5. Webhooks over polling: subscribe to webhook events instead of polling list endpoints; polling is the most common cause of rate limit exhaustion

​

Idempotency and retries