Rate limits

Snapcaster caps listing batch sizes, meters listing writes per seller, and rate-limits three other calls. Retries says how to retry a request over a limit.

A request above the cap returns BATCH_TOO_LARGE before any rate check or write. Split it into batches within the cap.

Snapcaster meters POST /listings, POST /listings/bulk and DELETE /listings per item and per seller, in one-minute windows. Each item in a batch counts as one unit. POST /listings/purge is not metered. The ceiling guards against abuse and sits above normal integration traffic. It is not a usage quota tied to your plan. In production, the ceiling is at least 100,000 listing items per minute per seller.

A request over the ceiling returns HTTP 429 RATE_LIMITED and writes nothing. Its Retry-After header is the time left in the current window, a whole number of seconds from 1 to 60. What to do after each failure says to wait that long, then send the same request.

If Snapcaster cannot reach the rate limiter’s backing store, it processes the request without the rate check, but the request caps above still apply.

Apart from the listing writes the item ceiling meters, Snapcaster rate-limits only these three operations.

Snapcaster rate-limits no read, so GET /orders and every other GET never return 429.