Amazon's new Selling Partner API: what changed, and what it means for your stack
Tighter rate limits, granular roles, and a much friendlier auth flow — here's what we rebuilt for SP-API v2.
Amazon's Selling Partner API has quietly become the backbone of every serious multichannel operation. The latest revision tightens rate limits, splits permissions into granular roles, and finally fixes the painful LWA refresh dance. Here's what changed and why your integration probably needs a tune-up.
Granular roles, not godmode tokens
The old MWS keys gave any integration the keys to the kingdom. SP-API v2 splits scope into pricing, inventory, orders, finance and brand analytics — each with its own approval flow.
We rewrote our auth layer so each Ctasis module requests only the scopes it actually needs. The result: cleaner audit trails and faster Amazon approvals.
One platform · every channel
Inventory, pricing and orders sync bi-directionally in real time.
A simplified view of what the system actually does behind the scenes.
Rate limits that punish polling
The new limits are forgiving for event-driven listeners and brutal for naive pollers. If your stack still hits /orders every 60 seconds, you're already throttled.
- Use Notifications (SQS/EventBridge) for order + pricing updates
- Cache catalog calls aggressively — they're the most expensive
- Backoff with jitter, not fixed retries
What we shipped for Ctasis sellers
Every Ctasis tenant now runs on SP-API v2 with per-module scopes, EventBridge subscriptions for orders and pricing, and a refresh-token rotation that just works. You don't have to think about it — and that's the whole point.
Tighter rate limits, granular roles, and a much friendlier auth flow — here's what we rebuilt for SP-API v2.
Talk to our team