Suppress an address from every message this store sends
Suppresses an address, so no message this store sends reaches it again. This is how an ESP forwards its own unsubscribes, bounces and complaints into the platform’s list, which is the reason this family is published at all. RE-ADDING AN ALREADY-SUPPRESSED ADDRESS IS NOT AN ERROR and does not move it. You get back the ORIGINAL reason and timestamp, so a complaint recorded last month is not restamped as today’s manual entry, and a webhook redelivery cannot turn into a retry storm. reason IS REQUIRED AND IS NOT DEFAULTED. It is a compliance record rather than a label: a spam complaint filed as a manual removal disappears from the store’s evidence that it stopped mailing when asked. THERE IS NO WAY TO REMOVE A SUPPRESSION THROUGH THIS API, deliberately. Removing one resumes mail to a person who bounced or complained, so no scope buys it; the merchant can do it from their own dashboard.
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.
Body
Both keys are required and NEITHER IS DEFAULTED. A missing reason would otherwise be filed as a manual removal, and a spam complaint recorded as a manual removal disappears from the store's evidence that it stopped mailing when asked. 201 EVEN ON A REPEAT, and the body is the suppression NOW IN FORCE, which on a repeat is the row already on file rather than the one you described. Compare the reason and created_at you get back against what you sent if you need to know which happened. Branching the status on that would leak whether an address is suppressed to a key holding only the write grant.
The address to suppress. It is stored VERBATIM, because this platform's send gate compares the stored address to the recipient exactly. Send it as your own system holds it rather than normalising first.
Why the address must not be mailed. It is a compliance record rather than a label, and a value outside the enum is a 400 rather than being coerced.
bounce, complaint, manual, unsubscribe Response
Created
