Limits
Limits are process-local token buckets with continuous refill, not fixed minute windows. A bucket starts full. Its refill rate is an admission ceiling, not guaranteed service throughput.
IP Limits
Ordinary request weight refills at 20000 tokens/second, up to 1200000 tokens. Dedicated pre-authentication IP buckets also apply to the documented account/fill, limit-price, public-market-data, cancel-replace, and wallet-challenge routes. A limiter rejection returns HTTP 429, whole-second Retry-After, and JSON code -1015.
API Key Limits
Authenticated requests are counted only after signature verification, against the verified key. API weight refills at 10000 tokens/second, with burst 600000. Effective rest.api-weight-enforced: false. When false, exhaustion is observational (would_block).
Order Count Limits
POST /order, DELETE /order, and POST /order/cancelReplace also count against Order Count. It refills at 10000 tokens/second, with burst 20000. Effective rest.orders-api-enforced: false. When false, exhaustion is observational (would_block).
Response Headers
X-PLEX-USED-WEIGHT-IP: Used tokens for the IP bucket.X-PLEX-USED-WEIGHT-API: Used tokens for the authenticated key, when accounting ran.X-PLEX-ORDER-COUNT: Used order tokens, when order accounting ran.
Used tokens are rounded maxBurst - remainingTokens, not calendar-minute totals. On a dedicated IP rejection, the IP header describes the rejecting bucket. No bucket-identifying header is emitted; use server limiter metrics to distinguish buckets.
Last updated