Overview

Amazon released the March 2026 change log for the Selling Partner API (SP‑API) on its developer portal, outlining fresh features, modifications to existing calls, and a timeline for retiring legacy endpoints. The update introduces new request throttling limits, revised error payload structures, and additional data fields across several operations. Sellers and solution providers must review the documentation promptly to adjust their integrations and avoid downtime.

Key Points

• Release notes available — The full March 2026 SP‑API changelog is posted on the Amazon developer console for public access.
• Deprecation timetable disclosed — A detailed schedule lists the exact dates when outdated API versions will stop processing requests.
• Throttling and schema changes — Updated rate‑limit rules and altered JSON schemas affect how calls are constructed and how responses are parsed.
• Sandbox testing urged — Amazon advises developers to validate every modification in the sandbox before promoting changes to production.
• 90‑day advance notice — Sellers receive at least a three‑month warning before any endpoint is retired, giving ample time for migration.

How the March 2026 SP‑API Release Works

1. Publication of change log — Amazon uploads a markdown document to the developer dashboard that enumerates every altered endpoint, new attribute, and deprecated operation; for instance, the “GetCatalogItem” call now includes a “fulfillmentAvailability” element in its response.
2. Release of deprecation schedule — A separate table specifies when each legacy version will be shut down, such as the “OrdersV0” API slated to cease on 30 September 2026.
3. Developer alerts — Registered developers receive an email and a portal notification summarizing the most impactful updates; an example alert highlights that the “SubmitFeed” endpoint now mandates a JSON‑formatted request body instead of the previous XML format.
4. Sandbox validation — The sandbox environment mirrors the production stack with the new limits and schemas, allowing developers to run end‑to‑end tests; a seller might issue a test order‑retrieval request and observe the revised pagination token structure.