Remove a shipping rate permanently
Removes the rate. There is no restore, and recreating is not restoring: the new row has a new id, and an order’s shipping_option_name is a snapshot rather than a link, so nothing joins the old rate back. NEEDS BOTH GRANTS. The qualified scope named above is refused to a key holding write_shipping alone. A deleted rate FAILS NOTHING: checkout simply stops offering that delivery method, shoppers in that region see fewer choices or none, and the only signal is a revenue line moving a week later. Use PATCH with is_active false to retire a rate reversibly; that needs only write_shipping. A missing option is a 404 rather than a silent 204, so a mistyped id cannot read as a successful removal while the merchant’s real rate keeps being offered.
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
Response
Success. The response has no body.
