orders_getOrder
Get one order (Orders v2026-01-01) with its line items inline (order.orderItems) and any included_data expansions.
readAmazon Seller (SP-API)sp.orders_2026-01-01
To find orders by date or status use orders_searchOrders. Amazon SP-API · getOrder · GET /orders/2026-01-01/orders/{orderId}
Call it
In an AI client (MCP)
{
"name": "orders_getOrder",
"arguments": {
"store": "myStore-US",
"order_id": "<order_id>"
}
}From code (Tool API)
curl -X POST https://api.sellersheetai.com/api/v1/tools/orders_getOrder \
-H "Authorization: Bearer $SELLERSHEET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"store":"myStore-US","order_id":"<order_id>"}'Early access — the Tool API is open on request, contact us.
Arguments
| Name | Type | Description |
|---|---|---|
storerequired | string | the store ref `<store>-<CC>` (name-country, e.g. 'myStore-US') — one of get_user_context's store_refs, verbatim. |
order_idrequired | string | e.g. '113-1234567-8901234'. |
included_data | string[] | expansion selectors; omit for the order and its line items with no expansions. PROCEEDS (revenue breakdown), EXPENSE (costs), PROMOTION (discounts), CANCELLATION, FULFILLMENT (how it ships, plus per-item quantityFulfilled / quantityUnfulfilled), PACKAGES (packages and tracking), TAX, PAYMENT (payment method), FULFILLMENT_ORDERS (linked MCF orders), RECIPIENT (order.recipient.deliveryAddress — city / countryCode / postalCode).RECIPIENTPROCEEDSEXPENSEPROMOTIONCANCELLATIONFULFILLMENTPACKAGESTAXPAYMENTFULFILLMENT_ORDERS |
Result
Every tool answers {notification, data, human_action}; data carries:
data.order— the order — line items at data.order.orderItems[], identifiers underdata.order.product— {orderItemId, quantityOrdered, product: {asin, title, sellerSku, condition, price}}.data.includedData— the selectors applied.
Gotchas
- Line items are not an includedData option — they come back on every call.
- Read item['product']['sellerSku'], not item['sellerSku']: the identifiers are nested under product, not flat on the item.