---
title: "Check whether an email is suppressed"
method: GET
path: "/api/suppression/{email}"
tags: ["Suppression"]
---

# Check whether an email is suppressed

`GET /api/suppression/{email}`

## Request

- Base URL: `https://api.sendly.now`
- URL: `https://api.sendly.now/api/suppression/{email}`
- Auth: one of:
  - HTTP bearer
  - API key in cookie `better-auth.session_token`
  - OAuth 2 (authorization code, authorization URL `https://app.sendly.now/api/auth/oauth2/authorize`, token URL `https://app.sendly.now/api/auth/oauth2/token`, scopes: `suppression:read`)

Returns `{ suppressed, reason?, source?, createdAt? }`. The path parameter must be URL-encoded.

Requires the `suppression:read` scope — View the addresses on your suppression list.

## Path parameters

- `email` string, required: URL-encoded email address

## Response `200`

Suppression check result

- SuppressionCheckResponse: Result of GET /api/suppression/{email} — whether the address is suppressed.
  - `createdAt` string, date-time: ISO 8601 datetime string
  - `reason` 'HARD_BOUNCE' | 'COMPLAINT' | 'MANUAL' | 'UNSUBSCRIBE'
  - `source` 'SES_WEBHOOK' | 'API' | 'DASHBOARD'
  - `suppressed` boolean, required

## Other responses

- `400`: Validation error
- `401`: Unauthorized — missing or invalid auth
- `403`: Forbidden — insufficient permissions or project disabled
- `429`: Rate limit or billing limit exceeded
- `500`: Internal server error

---

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