suppressions
Look up one suppressed recipient
GET /v1/suppressions/{email}
Auth required
api.suppressions.view
Returns the suppression record for an exact email address, or
404 not_found when the address is not on your SES suppression list.
Match is case-insensitive, but the returned email preserves SES's
stored casing. Newly-added suppressions can take up to a minute to
appear here. Percent-encode @ as %40 (e.g. user%40example.com).
Path parameters
email string<email> required Recipient address. Percent-encode @ as %40. Matched case-insensitively.
Responses
Errors follow the RFC 7807 problem format — see the error reference.
200 The suppression record application/json
email string<email> required reason string enum required One of: bounce, complaint, manual
suppressed_at string<date-time> required source string enum required One of: ses_event, manual
401 Missing, malformed, or unknown API key application/problem+json
403 Key lacks the required scope or plan limit violated application/problem+json
404 Resource not found application/problem+json
422 A query parameter, path value or body field failed validation.
The body is a
validation_failed Problem. When the refusal is about a
reference — a segment key, template slug, topic or attribute name the
organization does not have — it additionally carries validation_code,
field, line/column, missing, candidates and next_step, so a
client can correct the call without a second round of guessing. See
ValidationProblem.
application/problem+json 429 Per-org rate limit exceeded application/problem+json
500 Unexpected server-side failure. The
code is internal_error. The
request_id field can be quoted to SendOps support to investigate.
application/problem+json