API Ahead

Editions

API Ahead · Amazon SP-API — 27 May – 26 August 2026

What changed in the Amazon Selling Partner API between 27 May 2026 and 26 August 2026, and what it means for your code.

7 breaking · 6 silent risk · 113 additive · 12 announcements · 23 API models touched

Category Count
🔴 Breaking 7
🟠 Silent risk 6
🟢 Additive 113
📣 Amazon announcements 12

🔴 Breaking (7)

These will fail loudly. Fix before Amazon enforces them.

Amazon Warehousing And Distribution / awd_2024-05-09

  • Enum value(s) removed from GET /awd/2024-05-09/inboundShipments/{shipmentId}/labels :: pageType: LETTER_6, THERMAL_NONPCP
  • If you send any of these values the request will be rejected. If you store them, historical records may no longer validate.

Catalog Items API

  • Removed from Catalog Items API v0: listCatalogCategories (removal date: 2026-08-26)
  • If your integration still uses it, it is already failing in production.

Data Kiosk / analytics_salesAndTraffic_2023_11_15

  • API model removed: Data Kiosk / analytics_salesAndTraffic_2023_11_15
  • This API is gone from the published models. If you call it, confirm the retirement plan in the official changelog immediately.

Notifications API

  • Removed from Notification Type Values: LISTINGS_ITEM_ISSUES_CHANGE (payload version 1.0) (removal date: 2026-08-26)
  • If your integration still uses it, it is already failing in production.
  • Removed from Notification Type Values: ORDER_STATUS_CHANGE (removal date: 2026-07-29)
  • If your integration still uses it, it is already failing in production.

Orders / orders_2026-01-01

  • Field ItemProceedsBreakdown.subtotal is now required
  • Requests that omit it will be rejected.
  • Field ItemProceedsBreakdown.type is now required
  • Requests that omit it will be rejected.

🟠 Silent risk (6)

These will NOT fail at deploy time. They fail in production, later, on a subset of records. This is the section that costs people weekends.

Listings Items / listingsItems_2021-08-01

  • Allowed values now documented for Issue.categories[]: DUPLICATE, INVALID_ATTRIBUTE, INVALID_IMAGE, INVALID_PRICE, LISTING, MISSING_ATTRIBUTE, MISSING_IMAGE, MISSING_PRICE, PRODUCT, QUALIFICATION_REQUIRED
  • The field's type did not change, so a standard OpenAPI diff sees nothing here. But Amazon has now pinned down what this field can contain. If your code maps this field to a fixed set of values, check that every one of these is handled.

Notifications / OrderChangeNotification

  • New enum value(s) in OrderChangeNotification.Payload.OrderChangeNotification.OrderChangeType: DeliveryTipChange
  • This will NOT fail at deploy time. It fails in production the first time Amazon actually sends one of these values and your switch/map/match has no branch for it. Check every place you map this field to a fixed set of values.

Notifications / notifications

  • New enum value(s) in OrderChangeTypeEnum: DeliveryTipChange
  • This will NOT fail at deploy time. It fails in production the first time Amazon actually sends one of these values and your switch/map/match has no branch for it. Check every place you map this field to a fixed set of values.

Orders / orders_2026-01-01

  • New enum value(s) in GET /orders/2026-01-01/orders :: includedData: FULFILLMENT_ORDERS
  • This will NOT fail at deploy time. It fails in production the first time Amazon actually sends one of these values and your switch/map/match has no branch for it. Check every place you map this field to a fixed set of values.
  • New enum value(s) in GET /orders/2026-01-01/orders/{orderId} :: includedData: FULFILLMENT_ORDERS
  • This will NOT fail at deploy time. It fails in production the first time Amazon actually sends one of these values and your switch/map/match has no branch for it. Check every place you map this field to a fixed set of values.

Replenishment / replenishment-2022-11-07

  • New enum value(s) in AggregationFrequency: DAY
  • This will NOT fail at deploy time. It fails in production the first time Amazon actually sends one of these values and your switch/map/match has no branch for it. Check every place you map this field to a fixed set of values.

🟢 Additive (113)

New surface area. Nothing breaks — read only if you're curious.

Amazon Warehousing And Distribution / awd_2024-05-09

  • New schema: FormatType
  • New endpoint: GET /awd/2024-05-09/inboundShipments/{shipmentId}/labelPageTypes
  • New endpoint: GET /awd/2024-05-09/outboundOrders
  • New endpoint: GET /awd/2024-05-09/outboundOrders/{orderId}
  • New schema: InventoryDetailsVisibility
  • New schema: OrderAttribute
  • New schema: OrderPreference
  • New schema: OrderPreferenceValue
  • New schema: OutboundExecutionError
  • New schema: OutboundListing
  • New schema: OutboundOrder
  • New schema: OutboundOrderCreationData
  • New schema: OutboundOrderReference
  • New schema: OutboundShipment
  • New schema: OutboundStatus
  • New endpoint: POST /awd/2024-05-09/outboundOrders
  • New endpoint: POST /awd/2024-05-09/outboundOrders/{orderId}/confirmation
  • New endpoint: PUT /awd/2024-05-09/outboundOrders/{orderId}
  • New schema: PageType
  • New schema: ShipmentLabelPageTypes
  • New schema: ShipmentSortableField
  • New schema: SkuQuantitiesVisibility
  • New schema: SortOrder

Finances / financesInvoices_2026-06-25

  • New API model published: Finances / financesInvoices_2026-06-25

Finances / finances_2024-06-19

  • New schema: Balance

…and 88 more additive changes across 21 models.

📣 Amazon announcements (12)

What Amazon published in its changelog. Link and date; the summary is ours.

Listing attributes. Amazon updates the attributes and allowed values of product categories every month. That detail is not in the public models: it lives in the product type definitions served by the authenticated API, so we do not see it. Here you get the announcement and its date; the exact field that changed in your categories is part of the client service.

⏳ Upcoming removals (next 90 days)

What Amazon removes in the next 90 days according to its official schedule. Not this week's changes: the reminder so the migration does not catch you out.

Removal Product What goes away
26 August 2026 Catalog Items API v0 listCatalogCategories
26 August 2026 Notification Type Values LISTINGS_ITEM_ISSUES_CHANGE (payload version 1.0)
11 November 2026 Report Type Values GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE, GET_V2_SETTLEMENT_REPORT_DATA_XML

Sources: the OpenAPI models and the notification, report and feed schemas Amazon publishes, compared version to version; its official deprecations schedule and its changelog. Every change comes from one of these sources: nothing here is a guess.

API Ahead is free. It tells you what changed in the API.

If you'd rather be told what changed in your repo — the file, the line, and a pull request with the fix — that's what we're building next. Reply and we'll put you on the pilot list.

The OpenAPI models and schemas are © Amazon.com, Inc. or its affiliates, released under the Apache License 2.0. The deprecations schedule and the changelog belong to Amazon's documentation: we link to them and summarize them, never reproduce their content. This newsletter is an independent analysis of those public sources: it is not affiliated with, sponsored by, or endorsed by Amazon. Amazon and Selling Partner API are trademarks of Amazon.com, Inc. or its affiliates.