Fulfill Sales Order via FBA
POST/api/sales-orders/:salesOrder/fulfill-fba
Submits a Fulfilled-by-Amazon multi-channel fulfillment request for the sales order — Amazon picks, packs, and ships the selected lines out of FBA stock on your behalf. Only available in production environments.
orders:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Requires Bearer token.
Request body fields:
- warehouse_id (integer, optional): The Amazon FBA warehouse to fulfill from (must be an FBA-type warehouse). Auto-resolved when every product line on the order is routed to the same warehouse; required when lines span multiple warehouses.
- shipping_speed (string, required): Amazon shipping speed category. One of: Standard, Expedited, Priority.
- comments (string, required): Displayable order comment passed to Amazon.
- fulfillment_lines (array, optional, min 1 when present): Lines and quantities to fulfill. When omitted, defaults to every unfulfilled product line in the resolved warehouse at its full remaining quantity.
- fulfillment_lines.*.sales_order_line_id (integer, required): Sales order line to fulfill; must belong to the order and the resolved warehouse, and must not already be fulfilled.
- fulfillment_lines.*.quantity (number, required, >= 1): Quantity to fulfill; cannot exceed the line's remaining-to-fulfill quantity.
- fulfillment_lines.*.product_listing_id (integer, required): The Amazon product listing to ship for this line.
Behavior:
- The order must be approved (not draft) and not closed.
- On success, the fulfillment order is created at Amazon and the response includes the new fulfillment record ID and Amazon's request identifier.
- Outside production environments the request is rejected with an
IsUnacceptableerror and no fulfillment is created.
Path parameters:
- salesOrder (required): Sales order ID.
Requires permission: sales_orders.fulfill
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Unprocessable Entity
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.