Overview

Amazon has raised the request‑per‑second (RPS) limits for relationship‑focused operations in the Listings Items API. The adjustment applies to calls that create or modify parent‑child SKU links and package‑containment attributes, and it also speeds up the processing of JSON_LISTINGS_FEED files that carry relationship data. Sellers with large variation families should expect noticeably quicker bulk updates and reduced throttling incidents.

Key Points

• RPS ceiling tripled for relationship calls — The maximum rate for child_parent_sku_relationship and package_contains_sku requests has increased from 50 to 150 calls per second, cutting 429 throttling errors by roughly two‑thirds during massive uploads.
• Dedicated rate‑limit bucket — Relationship updates now draw from a separate quota, meaning they no longer compete with title, bullet, image, or price updates for the same token bucket.
• JSON_LISTINGS_FEED processing time slashed — Backend optimizations have reduced the average time to parse and validate relationship‑heavy feeds from about 12 minutes to under 4 minutes in internal tests.
• Scalability boost for catalogs over 50,000 SKUs — Sellers can push all variation changes in a single execution window instead of spreading the work across several hours, which was previously required to stay within throttling limits.
• Dynamic rate‑limit headers — The response header x-amzn-RateLimit-Limit now reflects the new per‑operation ceiling, enabling clients to adjust pacing in real time without hard‑coded delays.

How the Updated Listings Items API Works

1. Submit relationship payload — A developer sends a PATCH request containing a child_parent_sku_relationship array for, say, 5,000 child SKUs under a new parent ASIN; the API now accepts the call at 150 RPS instead of the former 50 RPS.
2. Route to relationship‑specific bucket — The request is directed to the newly created relationship quota, leaving the general product‑data bucket free for concurrent title, image, or price updates.