Remove a redirect permanently
Removes the redirect. IT TAKES NO BODY AT ALL, unlike the other writes on this api: the row is named entirely by the path and nothing is read from the request. NEEDS BOTH GRANTS. The qualified scope named above is refused to a key holding write_redirects alone, and the split is what this family is the plainest case for: a nightly importer that upserts is repaired by the next run, and one that deletes is not. NOTHING FAILS AT THE MOMENT IT HAPPENS, which is the whole hazard. The resource IS the repair for a dead link, so removing it restores the breakage: the old path 404s again, every inbound link and search result pointing at it dies, and the only signal is organic traffic falling off a week later. There is no deleted_at, no tombstone and no restore, and for a migrated store rebuilding means knowing which paths the store used to serve, which is thousands of rows nobody has a second copy of. No money and no stock move, and nothing is emitted. WHY IT EXISTS ANYWAY: from_path is immutable and the PATCH refuses it by name, so this is the only route to a corrected source path. Delete, then create the redirect again with the from_path you meant, which mints a new id. IDEMPOTENCY HERE IS PER KEY, NOT PER RESOURCE. Replaying the same Idempotency-Key returns the stored 204 without touching anything. A FRESH key against a redirect that is already gone is 404, because “your retry already landed” and “there is no such redirect” are different facts, and a 204 for a mistyped id would let a reconciliation record the row as removed while the real redirect kept answering.
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.