Selling Partner API for Orders

Name: Selling Partner API for Orders API
Brand: Selling Partner API for Orders
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceOrder Managementnone10 EndpointsREST

For Agents

Retrieve Amazon Selling Partner orders, buyer info, and line items, and confirm shipments through 10 SP-API Orders endpoints under /orders/v0.

Quickstart

Get started with Selling Partner API for Orders in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list recent Amazon Selling Partner orders"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

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

GET STARTED

Start building with Selling Partner API for Orders API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Selling Partner API for Orders, keeping it validated and agent-ready.

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.

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your LWA refresh token and SP-API IAM credentials are stored encrypted in the Jentic vault. Agents call operations through scoped Jentic tokens; Jentic exchanges the refresh token for a short-lived access token and signs the request server-side, so raw secrets never reach the agent.

Intent-based discovery

Agents search by intent (e.g., 'list Amazon orders' or 'confirm an Amazon shipment') and Jentic returns the matching SP-API Orders operations with their parameter shapes already resolved.

Time to first call

Direct SP-API integration takes 2-5 days for LWA setup, IAM signing, usage-plan back-off logic, and refresh-token rotation. Through Jentic the same operations are executable in under an hour.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Square

Commerce APIs covering catalog, orders, and in-person payments.

Choose Square when the seller is on Square commerce rather than Amazon, or needs unified online and POS orders.

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.

Complementary

SendGrid Mail Send

Transactional email delivery for shipping notifications.

Use SendGrid to send branded shipment confirmation emails after calling the SP-API shipmentConfirmation endpoint.

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 at https://app.jentic.com/sign-up.

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.