Overview

Amazon released the February 2026 update for the Selling Partner API (SP‑API) this week. The revision adds new endpoints, refines response structures, raises throttling caps, and sets a clear deprecation timetable. Sellers who rely on SP‑API must review the changes immediately to keep their integrations running and to leverage the new capabilities.

Key Points

• New operations added — The update introduces a health‑check call for inventory status and a bulk‑pricing update endpoint that can modify prices for up to 5,000 SKUs in a single request, cutting the time needed for large catalog adjustments.
• Response schema updates — Several existing calls now return richer JSON payloads; for example, the order-items endpoint includes a new fulfillmentChannel field that tells whether Amazon or the seller fulfilled each line item.
• Deprecation timeline clarified — A consolidated schedule lists legacy endpoints slated for removal by Q4 2026, giving developers a single reference point for migration planning.
• Throttling limits adjusted — Rate‑limit ceilings for high‑volume resources have been raised, allowing up to 15 requests per second for the feeds API, which benefits sellers pushing large batches of inventory or pricing data.
• Security enhancements — OAuth 2.0 token rotation is now mandatory every 12 hours, tightening access control and reducing the window for compromised credentials.
• Documentation overhaul — The release notes expand code samples in Python, Java, and Node.js, showing best‑practice patterns for pagination handling and exponential‑backoff retries.

How the February 2026 SP‑API Changes Work

1. Endpoint activation — Developers must register the February 2026 version in the Amazon Developer Console; once activated, calls such as bulkPricingUpdate become callable and can process price changes for thousands of SKUs in one payload.
2. Schema migration — Updated response formats require parsing logic adjustments; for instance, the parser must now capture the attribute to avoid null‑value errors in downstream fulfillment reports.