
Amazon Selling Partner API
Read Amazon orders, catalogue items, listings, FBA inventory, inbound shipments and reports, and create or patch listings and request reports for a seller account.
Bring Amazon marketplace orders, stock and listing health into ERP, warehouse and analytics flows, and keep listings in step with your product master.
Source actions
15
Destination actions
3
Data types
10
Validation status
Implemented · fixture tested.
Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.
What you can map
catalog items
- Get catalogue itemSource
An ASIN's summaries, attributes, identifiers, images, sales ranks and relationships.
catalog_items.get - Search catalogue itemsSource
Find Amazon catalogue items by keywords or identifiers (ASIN, EAN, UPC, GTIN, SKU).
catalog_items.search
fba inventory
- List FBA inventorySourceIncremental
Fulfilment-by-Amazon inventory summaries per SKU for the default marketplace.
fba_inventory.list
inbound plans
- Get inbound planSource
An inbound plan with its shipment IDs and statuses.
inbound_plans.get - List inbound plansSource
FBA inbound plans (Fulfillment Inbound v2024-03-20).
inbound_plans.list
inbound shipment items
- List inbound shipment itemsSource
SKUs and quantities in an FBA inbound shipment.
inbound_shipment_items.list
inbound shipments
- Get inbound shipmentSource
An FBA inbound shipment with destination, status, dates and tracking.
inbound_shipments.get
listings
- Get listingSource
A listing by SKU with summaries, attributes, offers, fulfilment availability and issues.
listings.get - Search listingsSourceIncremental
The seller's listings, optionally updated since a date, with status and issues.
listings.list - Patch listingDestinationProvider duplicate protectionApproval before production
Add, replace or merge listing attributes (for example price or quantity) with JSON patches.
listings.update - Create or replace listingDestinationProvider duplicate protectionApproval before production
Create or fully replace a listing for a SKU (putListingsItem) with product-type attributes.
listings.upsert
marketplace participations
- List marketplace participationsSource
Marketplaces the seller can sell in, with participation and suspension flags.
marketplace_participations.list
orders
- Get orderSource
One order with items, fulfilment, packages and proceeds.
orders.get - Search ordersSourceIncremental
Orders updated (or created) after a date in the selected marketplaces, with items, fulfilment and proceeds.
orders.list
report documents
- Get report documentSource
A finished report's pre-signed download URL and compression (valid for five minutes).
report_documents.get
reports
- Request reportDestinationNot retried automaticallyApproval before production
Request an asynchronous report (for example GET_MERCHANT_LISTINGS_ALL_DATA); poll Get report for its status.
reports.create - Get reportSource
A report's processing status and document ID when done.
reports.get - List reportsSource
Report requests by type and processing status.
reports.list
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, Amazon Fulfillment, 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, inbound 2/6, 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 and reports use nextToken (inventory tokens expire after 30 seconds).
Provider events
Notifications API (SQS/EventBridge) for order, listing and report events. Nexra event triggers are not yet available; flows run on demand or on a schedule.
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.
- Listing deletes, order cancellations, refunds and Merchant Fulfillment label purchases are not implemented.
- 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
- Create the Amazon credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Amazon Selling Partner API, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/amazon-selling-partner and the Connections API.