Peeker Partner API

Each organization shares one allowance across all its API keys. By default, it refills at 10 requests per second (600 requests per minute) and can burst to 600 requests. Creating extra keys does not increase capacity. Live and sandbox environments have separate limits. Reads and writes share the same allowance. An organization may have a custom limit, including a separate short-burst allowance and fixed minute budget. When you exceed it you get 429 rate_limited with details.retry_after_seconds and a matching Retry-After header in seconds. Wait that long, then retry with the same idempotency key when one was used.

Cloudflare import capacity

Live POST /domains/import can also return 429 rate_limited with details.reason: "cloudflare_account_capacity" when all eligible Cloudflare accounts are already handling synchronous imports. Use POST /domains/import/jobs for bulk async imports. That endpoint queues under the normal Partner API rate limit instead of rejecting because Cloudflare accounts are busy.

The 429 response

{
	"error": {
		"code": "rate_limited",
		"message": "API rate limit exceeded",
		"request_id": "550e8400-e29b-41d4-a716-446655440000",
		"details": {
			"retry_after_seconds": 12
		}
	}
}

HTTP status: 429; Retry-After: 12 for this example. Always pair it with the Peeker-Request-Id response header in your logs. The delay tells you when to try again; it does not reserve capacity against other requests.

Backoff with jitter

Honor retry_after_seconds, then add a small random delay so a fleet of workers does not sync into the next window.

# bash: wait the suggested time + 0-1 second jitter, retry once.
RESPONSE=$(curl -sS -o body.json -w "%{http_code}" \
  -H "Authorization: Bearer $PEEKER_KEY" \
  -H "Idempotency-Key: $IDEMPOTENCY_KEY" \
  -H "Content-Type: application/json" \
  -d "$BODY" \
  https://api.peeker.ai/partner/v1/orders)

if [ "$RESPONSE" = "429" ]; then
  WAIT=$(jq -r '.error.details.retry_after_seconds // 5' body.json)
  sleep "$(awk "BEGIN { print $WAIT + (rand() * 1) }")"
  curl -sS \
    -H "Authorization: Bearer $PEEKER_KEY" \
    -H "Idempotency-Key: $IDEMPOTENCY_KEY" \
    -H "Content-Type: application/json" \
    -d "$BODY" \
    https://api.peeker.ai/partner/v1/orders
fi

Live and sandbox are separate

pk_live_… and pk_test_… keep independent counters. You can hammer sandbox during integration without affecting live traffic.

Need more than 600/min?

Email support with your typical and peak request rates and we will raise the cap. We do not auto-throttle. Production accounts that need more get more.

Webhooks are not rate-limited

Webhook deliveries do not use your API quota. See Delivery and retries.

Concepts

Rate limits

Cloudflare import capacity

The 429 response

Backoff with jitter

Live and sandbox are separate

Need more than 600/min?

Webhooks are not rate-limited

​Cloudflare import capacity

​The 429 response

​Backoff with jitter

​Live and sandbox are separate

​Need more than 600/min?

​Webhooks are not rate-limited

Cloudflare import capacity

The 429 response

Backoff with jitter

Live and sandbox are separate

Need more than 600/min?

Webhooks are not rate-limited