---
title: "Delete a suppression"
method: DELETE
path: "/v1/suppressions/{id}"
tags: ["Suppressions"]
---

# Delete a suppression

`DELETE /v1/suppressions/{id}`

## Request

- Base URL: `https://smtpfa.st/api`
- URL: `https://smtpfa.st/api/v1/suppressions/{id}`
- Auth: HTTP bearer

Remove a suppression. The address becomes eligible for future sends unless it is suppressed again.

## Path parameters

- `id` string, required

## Response `200`

Suppression deleted

- SuppressionDeleted
  - `object` string, required
  - `suppression` string, required
  - `email` string, email, required
  - `deleted` boolean, required
  - `account_list` 'removed' | 'absent' | 'skipped' | 'failed', required: What happened at Amazon SES's account-level suppression list. Hard-bounce and complaint suppressions are released there too (removed, or absent when SES no longer had it); manual and unsubscribe suppressions are team-specific and skipped. failed means the local suppression is gone but SES could not be updated; a later send to the address may still bounce as OnAccountSuppressionList.

## Other responses

- `401`: Invalid or missing API key
- `403`: Forbidden - domain not verified or insufficient permissions
- `404`: Resource not found
- `429`: Rate limit exceeded - retry after the period indicated in the Retry-After header
- `500`: Internal server error

---

[API](https://skmtc.dev/smtpfa/apis/smtpfast-api.md) · [All operations](https://skmtc.dev/smtpfa/apis/smtpfast-api/llms.txt) · [OpenAPI document](https://skmtc.dev/smtpfa/apis/smtpfast-api/revisions/79dda742f53e?raw)