Overview

Amazon released the May 2026 version of its Selling Partner API (SP‑API) this week. The update adds fresh endpoints, tightens data schemas, raises request limits, and publishes a definitive retirement timetable for legacy calls. Sellers and developers who rely on Amazon’s marketplace APIs need to adjust their integrations now to avoid disruptions and to take advantage of the new data points.

Key Points

• New endpoints introduced — The May rollout brings additional resources that expose inventory‑health indicators and advertising‑performance metrics, expanding the data surface for automation.
• Schema updates — Revised JSON definitions now mandate extra attributes for order fulfillment and pricing, driving consistency across API interactions.
• Deprecation schedule announced — Amazon provides exact dates when older endpoints will cease, giving sellers a clear migration window.
• Standardized error payloads — All failure responses now follow a uniform structure with coded identifiers and human‑readable messages, reducing debugging effort.
• Higher rate limits — Select high‑volume operations receive larger request quotas, allowing bigger batch pulls without hitting throttling thresholds.
• Unified documentation portal — Release notes, deprecation timelines, and schema changes are consolidated into a searchable hub, simplifying reference for development teams.

How the May 2026 Changes Work

1. Endpoint activation — When a request targets one of the newly published resources, Amazon validates it against the latest schema and returns data in the new format. Example: A call to /listings/v2026-05-01/items now includes a “sell‑throughRate” field alongside quantity and price.
2. Schema enforcement — Calls that omit any of the newly required fields are rejected with a 400 Bad Request that contains a specific error code. Example: Submitting a createOrder payload without the mandatory object triggers an error response indicating the missing element.