Weekly newsletter · free · for Amazon SP-API developers

Find out what Amazon changed in the SP-API before it breaks your integration.

Every Monday, an exact diff of the OpenAPI models Amazon publishes, sorted into what breaks, what breaks silently, what is being retired and what is new. Every change comes from a public Amazon source you can check yourself: nothing comes from a guess.

It doesn't replace Amazon's changelog: it completes it. The changelog tells you what Amazon announces; we tell you what actually changed in the contract — models, notification and report schemas, rate limits and retirement dates — including what they didn't announce.

And what we don't see yet, said plainly: the attributes and allowed values of each product category are not in the public models; they live in the product type definitions served by Amazon's authenticated API. We tell you every time Amazon announces an update — it does so every month —; knowing which field changed in your categories is part of the service for customers.

Double opt-in · One-click unsubscribe · No spam, no bought lists · Privacy

The weekly email is in Spanish for now; every edition is also published in English on this site.

A real edition, not a mockup · May–August 2026

API Ahead · Amazon SP-API · 27 May – 26 Aug 2026

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

Catalog Items v0
listCatalogCategories is retired on 26 August 2026. The OpenAPI model still didn't mark it.
Data Kiosk
Amazon removes the analytics_salesAndTraffic_2023_11_15 schema.
awd_2024-05-09
Values LETTER_6 and THERMAL_NONPCP removed from the pageType parameter.
orders_2026-01-01
ItemProceedsBreakdown.subtotal and .type become required.
listingsItems_2021-08-01
10 Issue.categories values documented for the first time.
OrderChangeNotification
New value DeliveryTipChange in changeType.

How it works

A diff of versioned files. Deterministic and exact.

01

Amazon publishes its models

The OpenAPI models of the whole Selling Partner API live in a public Amazon repository, each change with its commit and date. Because that repository sometimes lags behind reality, we also read Amazon's official deprecation schedule and changelog.

Each model is flattened into facts

Instead of comparing two nested JSON documents, each document becomes flat statements with stable keys. Comparing two versions comes down to comparing two dictionaries.

field    Order.OrderStatus              -> string|required=True
enum-doc Issue.categories[]             -> ('DUPLICATE', 'INVALID_IMAGE', ...)
param    GET /orders :: includedData    -> array<string>|required=False|in=query

03

Each difference is classified and written up

Breaking, silent risk, deprecation or additive. Then, for every change that matters: what changed, what it breaks in practice and what to look for in your code. Written for a developer in a hurry.

The five categories

Not everything that changes breaks. What breaks doesn't always warn you.

Breaking	Fails loudly: endpoint or field removed, parameter that becomes required, enum value retired.
Silent risk	Doesn't fail at deploy time. Fails in production, weeks later, on part of your records.
Deprecation	Announced retirement. There's time, but there's a date.
Additive	New surface. Breaks nothing.
Amazon announcements	What Amazon publishes in its changelog, with its date and link.

The orange one is what sets us apart: a switch over the known values doesn't fail at deploy time; it fails the first time Amazon sends the new value.

Who it's for

For whoever maintains code against the SP-API.

Agencies and integrators who maintain N integrations for N clients. An Amazon change multiplies their work by N, and the first warning is usually an angry client.

ISVs and SaaS in the ecosystem whose product is the integration. If it breaks, it's not a bug: it's a product incident.

Teams with an in-house developer who also does ten other things and has no slot each week to read the changelog.

It's not for the seller who uses an off-the-shelf tool: that tool already has someone watching this for them. It's for that someone.

What's next

The next level: your repository, your file, your line.

We're building the next level: you connect your repository read-only and we tell you which file and which line each change touches, with a proposed pull request. Your code never leaves your premises and nobody writes to your production.

We're looking for the first pilot teams. Leave us your email and let's talk.

Also subscribes you to the weekly newsletter · Double opt-in · One-click unsubscribe · Privacy

Rather write directly? [email protected]

Every Monday, before your week starts.

No cost. No API keys. No access to your code.