Remove a segment and its membership
Removes the segment. Its materialised membership and refresh history cascade away with it and nothing announces the removal, so anything targeting the segment simply stops having an audience. PATCH status archived is the reversible form of the same intent. NEEDS BOTH GRANTS. The qualified scope named above is refused to a key holding write_segments alone, so ask the merchant for both. 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 segment that is already gone is 404 segment_not_found, because “your retry already landed” and “there is no such segment” are different facts.
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.
