List email suppressions
Every address this store must never mail again, whatever the message. It is published so you can honour the same suppressions in your own sending. It is not a mailing list, and treating it as a source of contactable people inverts its entire meaning. THERE IS NO GET BY ADDRESS because ?email= answers the same question better. “Is this address suppressed” returns an empty page when it is not, which is the correct answer; a 404 would be an error status for a perfectly normal outcome and every client would have to treat it as success. ADDRESSES ARE STORED AND MATCHED VERBATIM. This platform’s send gate compares the stored address to the recipient exactly, so filter on the address as you have it rather than normalising first: a lowercased query can report an address absent that the gate will not match either way.
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.
Query Parameters
EXACT match on one address, which is how you ask "is this address suppressed" before a send. An address that is not suppressed returns an empty page, which is the answer rather than an error. It is never a prefix or a pattern: that would turn a suppression list into a directory to enumerate by guessing. Send the address as you hold it. Matching is exact and so is this platform's own send gate, so normalising first can report an address absent that the gate will not match either.
Filter by why the address was suppressed. A value outside the enum is a 400 rather than an empty page: "nobody was suppressed for that reason" and "there is no such reason" are different facts, and a client told the former concludes its complaint feed arrived when it did not.
bounce, complaint, manual, unsubscribe Rows per page. Out of range is a 400 rather than a silent clamp, so a client asking for more than 100 learns it did not get it.
1 <= x <= 100The next_cursor from the previous page. Opaque: decode nothing from it and construct nothing by hand, since its encoding is not part of this contract. Omit it to read the first page.
