Complete a stock transfer and move the stock
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
Takes no parameters, and an empty body is expected. THIS is the call that moves stock, both legs in one transaction: the source level is decremented and the destination incremented by the transfer's own quantity. Partial completion does not exist in this model. Refuses with 409 insufficient_stock if the source cannot cover the quantity, and with 409 level_not_found unless both locations already stock the variant; in both cases nothing moved and the transfer is still requested. Replaying a completion answers 200 with the transfer and does NOT move the stock twice; completing a cancelled transfer is 409 invalid_transition.
Response
Success
