Skip to main content
GET
Get Recipient Suppression
Checks one exact recipient against Sequenzy’s bounce and complaint safeguards. This endpoint does not list unrelated recipients. Sequenzy suppresses recipients solely from its own bounce records. The email provider’s account-level suppression list is not consulted.

Request

string
required
Exact recipient email address. URL-encode the value when constructing the request URL.
string
deprecated
Accepted and ignored. It previously limited a provider-side suppression lookup, which no longer happens.

Response

local.scope describes how far a local suppression reaches: global when the SMTP evidence conclusively identified an invalid destination and every workspace is blocked, company when the block is contained to your workspace (an ambiguous hard bounce, repeated delivery failures of your own sends, or a spam complaint against your email). Global invalid-recipient suppressions are protected; only company-scoped soft-bounce escalations can be removed. It is null when the address is not locally suppressed. Use List Suppressed Recipients to see every suppressed address at once. local.suppressionType uses the same stable values as the list: invalid_recipient, unknown_hard_bounce, soft_bounce_escalation, or complaint. local.delistable is true only for soft_bounce_escalation. knownRecipient indicates whether the address appears in this company’s subscriber or email-send history. Unknown addresses return an empty result so the endpoint cannot be used to probe suppressions belonging to another company. The ses object is deprecated and always returns regionsChecked: [] and entries: []. It is retained so existing integrations keep parsing. Read suppressed and local instead.