Lift a cart-recovery suppression
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. ONLY A bounce OR A manual SUPPRESSION CAN BE LIFTED. unsubscribe and complaint are the shopper's own decision, are honoured everywhere, and are refused 403 optout_not_liftable naming the reason that was found. A bounce is a delivery fact that can go stale (a full mailbox, a misconfigured domain), and manual is your own entry, so both are yours to revisit. THE ADDRESS IS THE PATH SEGMENT: this resource publishes no id and its natural key is the email, stored lowercased and trimmed. Percent-encode it like any path segment. An address with no suppression is a 404 rather than a 204, because a fresh Idempotency-Key against one means you believe a suppression is there; a REPLAYED key still returns the stored 204.
Response
Success. The response has no body.