Delete an email suppression
DELETE
/v1/email/suppressions/{suppression_id}
// Check for remaining blocking records before resuming delivery.
await bird.suppressions.remove("sup_abc123");# An API key cannot remove a `complaint` record; those come off in the dashboard.
client.suppressions.remove("sup_abc123")// Check for remaining blocking records before resuming delivery.
if err := client.Suppressions.Remove(context.Background(), "sup_abc123"); err != nil {
log.Fatal(err)
}// An API key cannot remove a `complaint` record; those come off in the dashboard.
$bird->suppressions->remove('sup_abc123');bird email suppressions remove <suppression-id> --yescurl -X DELETE "https://us1.platform.bird.com/v1/email/suppressions/{suppression_id}" \
-H "Authorization: Bearer $TOKEN"Permanently deletes the selected suppression record. Other blocking records for the address remain in effect. Deletion cannot be undone. If the address hard-bounces or the recipient complains again, a new suppression is created automatically.
Most records exist because the address bounced or complained. Resuming delivery without cause can harm sender reputation. An address suppressed for several reasons has one record per reason. Delete each blocking record to re-enable delivery. To find a record by address, use GET /v1/email/suppressions with the email parameter. An ID that does not exist in the workspace returns 404.
A record with reason complaint can only be deleted by a signed-in dashboard user; an API key gets 422 (SuppressionNotRemovableByAPIKey). hard_bounce and manual records are unaffected and stay removable either way.
Parameter
suppression_id
string
ID of the suppression record, as returned when the suppression was created or listed.
Verwandte Ressourcen
Weiter mit der Dokumentation, Anleitungen und Beispielen zu diesem Thema. Die Ressourcen sind auf Englisch.
Anleitung ansehenWhat happens when someone opts outDas Konzept verstehenWhat is one-click unsubscribe, and how do I implement List-Unsubscribe?Die Funktion erkundenEmail opt-outsDem Lernpfad folgenOperate messaging reliably
Implementierungs-Briefing erhalten