Overview

Amazon has released technical documentation outlining significant modifications to the Selling Partner API (SP-API) ecosystem scheduled for September 2026. These updates represent a fundamental shift in how Amazon’s backend data structures communicate with third-party software, moving toward more complex and secure data models. Sellers who rely on external tools for inventory, order management, or financial reporting must prepare for these changes to avoid critical operational disruptions.

Key Points

• Implementation Window — The scheduled technical updates will be rolled out across the entire month of September 2026.
• Schema Evolution — Amazon is transitioning from flat data structures to hierarchical JSON objects to improve data precision.
• Endpoint Retirement — Legacy API endpoints used for older reporting methods are being phased out in favor of modernized, more efficient paths.
• Security Hardening — The update mandates stricter enforcement of OAuth 2.0 protocols to protect seller account data.
• Traffic Management — New throttling thresholds and granular rate-limiting rules are being introduced to better manage high-volume request traffic.
• Data Validation — Stricter payload validation rules will be implemented, meaning previously optional fields may become mandatory for successful requests.

What's Changing

The September 2026 release is a modular series of updates rather than a single software patch. Technical teams must address several distinct areas of the API architecture to maintain connectivity.

1. Hierarchical Data Migration — Amazon is moving away from simple, single-string data fields toward nested, structured JSON objects. For example, instead of receiving a single "address" string containing all location details, developers will now receive a structured "address_object" that separates the street, city, postal code, and country into individual, discrete fields.
2. URL and Endpoint Redirection — The API is undergoing a structural reorganization of its paths. Developers will need to update their software to point to new routes, such as migrating from outdated reporting paths to the updated or moving order-related calls to the new endpoints. Requests sent to deprecated URLs will eventually trigger 404 or 410 error codes.