---
title: "Update an email exception blacklist rule"
method: PUT
path: "/v3/contact-blacklist-rules/email-exceptions/{id}"
tags: ["Contact Blacklist Rules"]
---

# Update an email exception blacklist rule

`PUT /v3/contact-blacklist-rules/email-exceptions/{id}`

<small>_Requires the `contacts:write` scope (or a broader one that includes it)._</small>

Updates an existing email exception blacklist rule.

## Path parameters

- `id` integer, required

## Request body

- object — Request body for updating an email exception blacklist rule
  - `pattern` string, required — Email address to allow as exception. Must be a valid email format (e.g., `user@example.com`)

## Response `200`

Email exception blacklist rule updated successfully

- object — An exception rule that allows an email pattern even if it matches a blacklist rule
  - `id` integer — Unique identifier of the rule
  - `pattern` string — Email pattern to allow as exception

## Other responses

- `400` — Route parameter / body validation failure (e.g. pattern is not a valid email)
- `401` — Unauthorized. The response body is empty; check the `WWW-Authenticate` header for the expected scheme.
- `403` — User lacks required feature scope to manage blacklist rules
- `404` — Email exception blacklist rule not found
- `409` — A rule with the given pattern already exists
- `429` — Too Many Requests

---

[API](https://skmtc.net/reply/apis/reply-api.md) · [All operations](https://skmtc.net/reply/apis/reply-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/reply/reply-api/versions/1c3d32eaf95e/schema)