Retrieve an order margin
What one order made, in the same shape the list serves, so a row read from a page can be re-read on its own rather than by walking the collection again. That is how a client picks up a refund issued since it last synced. THE PATH TAKES THE ORDER ID, which is this resource’s own id: there is one frozen margin per order forever, so the order’s id is the only handle it has and no separate margin id exists. It is the same value the orders family hands you. A 404 HERE IS margin_not_available AND IT DOES NOT MEAN “no such order”. An order placed before margin tracking began and an id that names nothing answer identically on purpose, because telling them apart would mean resolving the order and turning this grant into a probe for which order ids exist in the store. Do not go looking for a bug in your order sync when you meet it.
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.
Path Parameters
Response
Success
