Create a fulfillment against an order
Authorizations
A secret API key. Publishable keys cannot reach this API. A key may carry an expiry, and an expired key is refused exactly like an unknown one, with a 401 that names no reason; check the key's expires_at in the dashboard rather than inferring it from a response. When a merchant rolls a key's secret they choose a grace window of up to 3 days, and for its duration BOTH the new secret and the one it replaced authenticate, so an integration moves over on its own deploy schedule instead of at the instant the button is pressed. Move before the window closes: after it, the old secret is refused. Nothing else about this contract moves with a roll. The key keeps its id and its scopes, so the only thing an integration updates is the credential itself.
Headers
A unique key per logical write. Replaying a request with the same key returns the first response byte for byte instead of applying the write twice.
Path Parameters
Body
Creates the shipment as PENDING and notifies nobody. Handing it to a carrier, which is what mails the shopper, is POST /fulfillments/{fulfillmentId}/ship. The order must be paid or already fulfilled. To ship part of an order, create two fulfillments and ship each; a fulfillment ships all of its own lines in one statement.
The order lines this shipment covers. Addressed by order_line_item_id, which the v1 order read and the fulfillments/created webhook both publish, never by variant id.
1 - 500 elementsResponse
Created
