Overview

Starting May 1 2023, Amazon will tighten the request ceiling for the getItemOffersBatch call in the Product Pricing API, dropping it from 0.5 to 0.1 requests per second. The companion getListingOffersBatch endpoint will keep its existing 0.5‑rps limit, meaning only one of the two bulk‑offer methods will face a stricter cap. Sellers who automate price collection must adjust pacing, error handling, and overall refresh cycles to stay within the new boundaries.

Key Points

• New throttle level — The getItemOffersBatch endpoint will allow only one call every ten seconds, a five‑fold reduction from the previous half‑call‑per‑second rate.
• Sibling endpoint unchanged — getListingOffersBatch continues to accept up to five calls in ten seconds, so workflows that can switch to it will retain higher throughput.
• All marketplaces affected — The revised limit applies to every region where the Product Pricing API is available, including the United States, Canada, Europe, Japan, and Australia.
• Higher 429 risk — Exceeding the 0.1 rps threshold will generate HTTP 429 “Too Many Requests” responses, forcing batch jobs to incorporate throttling safeguards.
• Potential cost rise — Slower request pacing may lengthen execution time for Lambda, EC2, or other compute resources, leading to modestly higher operating expenses.
• Effective date — The change takes effect at 00:00 UTC on May 1 2023; any integration still sending requests at the former speed after that moment will be throttled automatically.

How the Throttle Change Works

1. Request submission — Amazon now permits a single getItemOffersBatch call per ten‑second window; for instance, a script that previously fired ten calls within ten seconds must pause after the first call and wait nine seconds before issuing the next.
2. Rate‑limit feedback — When a request breaches the limit, the API returns a header (e.g., ) alongside the 429 status, indicating exactly how long the client should wait before retrying.