createOrder

post

https://sellingpartnerapi-na.amazon.com/fulfillment/outbound/2026-07-04/orders

Request that Amazon ship items from the seller's inventory in Amazon's fulfillment network to a destination address.

Usage Plan:

Rate (requests per second)	Burst
2	30

The x-amzn-RateLimit-Limit response header returns the usage plan rate limits that were applied to the requested operation, when available. The preceding table indicates the default rate and burst values for this operation. Selling partners whose business demands require higher throughput may see higher rate and burst values than those shown here. For more information, see Usage Plans and Rate Limits in the Selling Partner API.

Body Params

The request body schema for the createOrder operation.

The request body schema for createOrder.

orderId

string

required

A fulfillment order identifier that the seller creates to track their fulfillment order. The orderId must be unique for each fulfillment order that a seller creates. If the seller's system already creates unique order identifiers, then these might be good values for them to use.

channel

string

length ≤ 40

The sales channel of the fulfillment order.

fulfillmentConfiguration

object

Fulfillment configuration for an order request.

origin

object

The origin of the fulfillment.

destination

object

required

The destination of the fulfillment order.

lineItems

array of objects

required

A list of items to include in the fulfillment order, including quantity.

lineItems*

paymentInformation

object

Payment information for the order. Currently only available in India.

Headers

x-amzn-fulfillment-service-id

string

length ≤ 40

The identifier of the fulfillment service used for this operation.

Responses

Language

Loading…

Response

Choose an example:

application/json

200Success.

202Accepted.

400Request has missing or invalid parameters and cannot be parsed.

401The request's Authorization header is not formatted correctly or does not contain a valid token.

403Indicates that access to the resource is forbidden. Possible reasons include Access Denied, Unauthorized, Expired Token, or Invalid Signature.

404The resource specified does not exist.

413The request size exceeded the maximum accepted size.

415The request payload is in an unsupported format.

429The frequency of requests was greater than allowed.

500An unexpected condition occurred that prevented the server from fulfilling the request.

503Temporary overloading or maintenance of the server.