suppressed_recipient

Status: 422 · Code: suppressed_recipient

Every recipient on the send is on your workspace's suppression list, so the send was rejected before it went to a queue. If only some recipients were suppressed, the send goes through for the rest — and we record a suppressed event for each one we dropped.

Why we do this

Sending to a known-bad address hurts your domain reputation for the other customers on the same IP pool. Once an address bounces hard, complains, or unsubscribes, we add it to your suppression list automatically.

How to fix

First, check the list:

curl -H "Authorization: Bearer $SEND0_API_KEY" \
  https://api.send0.dev/v1/suppressions

Then decide:

• The suppression is correct — don't send. Remove this address from your outbound list upstream.
• You know the suppression is stale (e.g., user asked to be re-subscribed) — remove from the list:

  curl -X DELETE -H "Authorization: Bearer $SEND0_API_KEY" \
    https://api.send0.dev/v1/suppressions/{id}

  Then retry the send.

Removals are logged to audit — we track who unsuppressed whom, in case compliance asks.

Related

• Suppressions API
• Webhooks: email.bounced + email.complained