Amazonservices Selling Partner API for Orders
Agent-ready OpenAPI document · curated by JenticE CommerceOrder Managementnone10 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Retrieve Amazon Selling Partner orders, buyer info, and line items, and confirm shipments through 10 SP-API Orders endpoints under /orders/v0.
Use for: List my Amazon orders from the last 24 hours, Get the line items for a specific Amazon order, Pull the shipping address for an order, Confirm shipment of an Amazon order
Not supported: Does not handle Amazon listings, FBA inventory, advertising, finances, or reports - use for SP-API Orders v0 retrieval and shipment confirmation only.
Jentic publishes the only available OpenAPI specification for the Selling Partner API for Orders, keeping it validated and agent-ready. The Orders API is part of Amazon's Selling Partner API (SP-API) suite and lets sellers retrieve order details, buyer information, shipping addresses, line items, regulated-product data, and confirm shipments. The 10 endpoints under /orders/v0 cover the order lifecycle from listing and inspection through shipment confirmation. SP-API uses LWA (Login with Amazon) OAuth 2.0 access tokens plus signed requests in production; the spec itself does not declare a security scheme so callers must layer SP-API auth at runtime.
Install Jentic One Beta
Connect the Selling Partner API for Orders to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Selling Partner API for Orders, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdeveloper.amazonservices.com%2Famazon-spapi-orders" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdeveloper.amazonservices.com%2Famazon-spapi-orders" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Selling Partner API for Orders API.
List Amazon orders within a marketplace and date range via GET /orders/v0/orders
Get a single order by id via GET /orders/v0/orders/{orderId}
Read buyer info and shipping address via /orders/v0/orders/{orderId}/buyerInfo and /orders/v0/orders/{orderId}/address
Pull order line items via GET /orders/v0/orders/{orderId}/orderItems
Read or update regulated-product data via GET and PATCH /orders/v0/orders/{orderId}/regulatedInfo
Confirm an order shipment via POST /orders/v0/orders/{orderId}/shipment and POST /orders/v0/orders/{orderId}/shipmentConfirmation
Use Cases
Patterns agents use Selling Partner API for Orders API for, with concrete tasks.
★ Order ingestion into a fulfillment system
Ingest Amazon orders into a warehouse or 3PL system by polling GET /orders/v0/orders with CreatedAfter and MarketplaceIds, then for each order fetch /orderItems and /address to drive the pick, pack, and label flow. The spec models the SP-API Orders surface so the calling system always sees the canonical Amazon order shape, including marketplace, buyer, and item-level data.
GET /orders/v0/orders?MarketplaceIds=ATVPDKIKX0DER&CreatedAfter=2026-06-09T00:00:00Z, then for each AmazonOrderId GET /orders/v0/orders/{orderId}/orderItems to load lines into the WMS.
Shipment confirmation back to Amazon
After fulfillment, confirm the shipment with Amazon through POST /orders/v0/orders/{orderId}/shipmentConfirmation, supplying the carrier, tracking number, and shipping method. POST /orders/v0/orders/{orderId}/shipment is the legacy entry point still exposed by SP-API. Confirming on time is essential to avoid Amazon's late-shipment metrics impacting seller account health.
POST /orders/v0/orders/{orderId}/shipmentConfirmation with body containing the carrier, trackingNumber, and shipMethod for each shipped order.
Regulated product compliance
For categories such as alcohol, tobacco, or pharmacy where Amazon enforces regulated-product workflows, the API exposes /orders/v0/orders/{orderId}/regulatedInfo. GET returns the regulated information attached to the order and PATCH updates the rejection reason or compliance status. This lets a seller's compliance system stay in sync with Amazon for restricted-category orders.
GET /orders/v0/orders/{orderId}/regulatedInfo to inspect compliance state, then PATCH the same path with regulatedOrderVerificationStatus when a verification step completes.
Agent-driven Amazon order operations
An AI ops agent can answer seller questions like 'which orders are unshipped from yesterday?' by calling the SP-API Orders endpoints through Jentic. Jentic returns the operation schemas and runs the call with the seller's LWA token from the vault, so the seller's Amazon credentials never enter the agent's context.
Through Jentic, search 'list recent Amazon orders', load the /orders/v0/orders operation, and execute it with CreatedAfter set to 24 hours ago and OrderStatuses=Unshipped.
Key Endpoints
10 endpoints — jentic publishes the only available openapi specification for the selling partner api for orders, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/orders/v0/orders
List Amazon orders by marketplace and date range
GET
/orders/v0/orders/{orderId}
Get a single order
GET
/orders/v0/orders/{orderId}/orderItems
List line items on an order
GET
/orders/v0/orders/{orderId}/address
Get the shipping address for an order
GET
/orders/v0/orders/{orderId}/buyerInfo
Get buyer information for an order
POST
/orders/v0/orders/{orderId}/shipmentConfirmation
Confirm shipment of an order
PATCH
/orders/v0/orders/{orderId}/regulatedInfo
Update regulated-product compliance data
GET
/orders/v0/orders
List Amazon orders by marketplace and date range
GET
/orders/v0/orders/{orderId}
Get a single order
GET
/orders/v0/orders/{orderId}/orderItems
List line items on an order
GET
/orders/v0/orders/{orderId}/address
Get the shipping address for an order
GET
/orders/v0/orders/{orderId}/buyerInfo
Get buyer information for an order
POST
/orders/v0/orders/{orderId}/shipmentConfirmation
Confirm shipment of an order
PATCH
/orders/v0/orders/{orderId}/regulatedInfo
Update regulated-product compliance data
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Selling Partner API for Orders by hand means running the LWA token exchange, signing each request, and picking the right regional Selling Partner host such as the North America endpoint. Through Jentic you install once, import the Selling Partner API for Orders from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
The order id travels in the URL path (/orders/v0/orders/{orderId}/...), so a rule can pin your agent to reads for a given order and its items, address, and buyer info. You choose the operations it may call, so state-changing ones like posting a shipment confirmation or patching regulated info are not included unless you add them.
Credential isolation
Your LWA refresh token and Selling Partner credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list Amazon orders' or 'confirm an Amazon shipment', and Jentic returns the matching Selling Partner Orders operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Complementary
Stripe
Payments, refunds, and dispute APIs.
Use Stripe alongside SP-API Orders when reconciling settlement, refunds, or chargebacks for a seller's external Stripe account.
FAQs
Specific to using Selling Partner API for Orders API through Jentic.
Why is there no official OpenAPI spec for Amazon SP-API Orders?
Amazon publishes Swagger-style models on its SP-API GitHub but does not publish a single curated OpenAPI 3 specification scoped to the Orders v0 surface. Jentic generates and maintains this spec so that AI agents and developers can call SP-API Orders via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Amazon SP-API Orders API use?
SP-API uses LWA (Login with Amazon) OAuth 2.0 access tokens plus AWS Signature Version 4 signing. The OpenAPI spec does not declare these schemes inline, so callers must layer SP-API auth at runtime. Through Jentic, LWA refresh tokens and SP-API IAM credentials are stored in the vault and exchanged into short-lived access tokens at execution time, so the agent never sees the raw secrets.
Can I confirm a shipment back to Amazon with this API?
Yes. POST /orders/v0/orders/{orderId}/shipmentConfirmation with the carrierCode, trackingNumber, and shipMethod confirms the shipment. POST /orders/v0/orders/{orderId}/shipment is the legacy variant still exposed by SP-API and remains in this spec.
What are the rate limits for SP-API Orders?
Amazon enforces per-operation usage plans for SP-API; Orders endpoints have small per-second rates with burst quotas. The OpenAPI spec does not encode the limits, so check Amazon's SP-API usage plans documentation for current values and treat HTTP 429 as a signal to back off.
How do I list yesterday's unshipped Amazon orders through Jentic?
Through Jentic, search 'list recent Amazon orders', load the /orders/v0/orders operation, and execute it with MarketplaceIds set to your marketplace, CreatedAfter set to 24 hours ago, and OrderStatuses=Unshipped. Jentic handles LWA token exchange and request signing.
Can I read buyer contact info from this API?
GET /orders/v0/orders/{orderId}/buyerInfo returns buyer email and name where the marketplace allows it, and GET /orders/v0/orders/{orderId}/address returns the shipping address. Visibility is governed by Amazon's data access policies for SP-API roles, and personally identifiable buyer data is restricted.
Can I limit what my agent is allowed to do with the Amazon SP-API Orders API?
Yes. Because you run Jentic One yourself, your own rules decide which SP-API Orders operations the agent may call and which credentials it may use. Since the order id travels in the URL path (/orders/v0/orders/{orderId}/...), you can pin the agent to read operations for a given order and its items, address, and buyer info while excluding state-changing calls such as POST shipmentConfirmation or PATCH regulatedInfo. Those operations run only if you explicitly add them to what the agent is allowed to do.
GET STARTED