Amazon Selling Partner API

Access and limits

Authentication

Login with Amazon (LWA) client ID, client secret and refresh token

Plans and access

Requires a Professional seller account and a registered SP-API developer application. Each operation needs the matching application role (Inventory and Order Tracking, Product Listing, Pricing, Finance and Accounting, Amazon Fulfillment, Buyer Communication, Selling Partner Insights). Buyer and shipping-address data needs a Restricted Data Token, which this connection does not request.

Test environment

Static sandbox endpoints (sandbox.sellingpartnerapi-*.amazon.com) return canned responses; use a private application on a test seller account for realistic testing.

Rate limits

Per-operation token buckets (requests per second / burst): searchOrders 0.0056/20, getOrder 0.5/30, searchCatalogItems and getCatalogItem 2/2, listings get/put 5/10, patch and search 5/5, FBA inventory 2/2, createReport 0.0167/15, getReports 0.0222/10, getReport 2/15, getReportDocument 0.0167/15, feeds 0.0222/10, inbound 2/6, finances 0.5/30, fee estimates 1/2, item offers 0.5/1, order metrics 0.5/15, messaging 1/5, marketplace participations 0.016/15. x-amzn-RateLimit-Limit reports the applied rate; HTTP 429 when exceeded.

Pagination

Orders use paginationToken, catalogue and listings use pageToken (max 20 per page), FBA inventory, finances, reports and feeds use nextToken (inventory tokens expire after 30 seconds), inbound uses paginationToken.

Provider events

Notifications API (SQS/EventBridge) for order, listing and report events. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.

Before you build a flow

• Orders use the Orders API v2026-01-01 (v0 is deprecated); buyer and recipient PII needs a Restricted Data Token and is not requested.
• Reports are asynchronous: create a report, poll its status, then read the document metadata. The document is a pre-signed S3 URL on another host that Nexra does not download.
• Listings writes return ACCEPTED or INVALID submissions; Amazon processes them asynchronously, so check issues on the listing afterwards.
• Intentionally excluded: listing deletes, order cancellations, refunds, shipment confirmation, label purchases (Merchant Fulfillment and Shipping v2), inbound plan creation or confirmation, feed and report cancellation, notification subscription or destination changes, and sending buyer messages.
• Feed creation is not implemented: a JSON_LISTINGS_FEED upload goes to a pre-signed S3 URL on a per-request host, which the recipe engine cannot allow safely. Feed status and result document reads are available, and the Listings Items API covers single-SKU writes.
• Restricted operations (buyer info, shipping addresses, regulated info) need a Restricted Data Token flow the engine does not support, so they stay out.
• Finances, offers, fee estimates, order metrics, messaging actions and tracking are read only. Fee estimates call a POST endpoint but charge nothing.
• Financial events carry no Amazon ID; Nexra derives a stable record ID by hashing each event.
• Notification destinations are grantless operations and are not offered; subscriptions are read per notification type.
• Amazon documents no idempotency key; report requests are not repeated automatically when the outcome is uncertain.
• Grantless operations and the static sandbox hosts are not offered.

Developer reference