MWS (Marketplace Web Services)

Amazon & D2C glossary · Harpy Media

MWS (Marketplace Web Services) was Amazon’s original programmatic interface for sellers: the API that let software connect to Seller Central data, automating inventory, orders, payments, and reporting. For over a decade it was the plumbing of professional automation on the marketplace.

What is MWS?

MWS (Marketplace Web Services) was Amazon’s original programmatic interface for sellers: the API that let software connect to Seller Central data, automating inventory, orders, payments, and reporting. For over a decade it was the plumbing of professional automation on the marketplace.

It has been fully deprecated and replaced by the Selling Partner API (SP-API) — the modern, more secure successor. The historical fact is simple; the practical danger is not. Any integration still calling the old MWS endpoints is a live failure waiting to happen, and when it fails, it fails silently and completely.

What MWS was, and why the transition matters

MWS let developers build tools that queried Amazon’s databases directly: pulling order feeds, pushing inventory updates, retrieving reports. Software suites and custom apps relied on it to run the back office — order downloads, stock syncs, pricing updates, financial reporting — without human intervention.

SP-API modernised all of that: different authentication, different endpoints, finer-grained permissions, stronger security. The functional replacement is complete, but the migration lives in your software stack, not in Seller Central — which means it can be overlooked for exactly as long as everything appears to be working. The failure arrives on the day legacy credentials stop being honoured.

What happens to un-migrated integrations

Legacy developer tokens and old endpoints are deactivated. When that happens to your stack: order data stops downloading, so automated shipping lines freeze; inventory ledgers go stale, so availability drifts from reality; pricing scripts stop updating; reporting feeds empty out. None of these announce themselves — the software simply stops doing its job while the business carries on.

The downstream damage is account-level. Orders that never flow to the warehouse turn into late shipments; stale inventory data turns into oversells or accidental stockouts; and by the time the break is noticed, the metrics have already moved. Migrations are cheap decisions made early and expensive emergencies made late.

In practice

A brand runs modern software: its application holds an authorised SP-API token, monitors inventory levels across fulfilment centres, receives instant order notifications, updates its ledger, and triggers automated pricing scripts to hold margins. Data flows smoothly, no one thinks about authentication, and the operation scales without attention — which is precisely what a healthy integration is supposed to feel like.

How Harpy Media helps

Tooling and automation reviews are part of our operations setup: mapping every integration, confirming SP-API status, and building the manual fallbacks that keep orders moving if software breaks. Automation is leverage — right up until the credentials expire.

MWS FAQ

Is MWS still usable?

No — Marketplace Web Services has been deprecated and superseded by the Selling Partner API. Integrations still pointed at MWS endpoints will fail as legacy access is retired; they must be migrated to SP-API to keep functioning.

How do I know if my tools still use MWS?

Ask each software vendor directly and get the answer in writing; check the tool documentation for API references; and review any custom-built application with its developer. If no one can confirm SP-API usage, assume the integration needs an audit.

What is the Selling Partner API?

Amazon’s current programmatic interface — the modern replacement for MWS, with finer-grained permissions, stronger authentication, and support for sellers, vendors, and partners. All current automation should run on it.