---
title: "Revoke CASL consent for an email address"
method: DELETE
path: "/v1/compliance/consents/email/{address}"
tags: ["Compliance / CASL"]
---

# Revoke CASL consent for an email address

`DELETE /v1/compliance/consents/email/{address}`

## Request

- Base URL: `https://api.honkio.ca`
- URL: `https://api.honkio.ca/v1/compliance/consents/email/{address}`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`

Revokes the ACTIVE email consents for the address. Commercial email to it is then refused with EMAIL_NO_CONSENT until consent is recorded again; transactional email is unaffected. Opt-outs and suppressions are separate.

Requires `compliance:m` or `compliance:d` (any of).

## Path parameters

- `address` string, required

## Response `204`

Every active consent for the email address is revoked.

## Other responses

- `401`: Missing, invalid, revoked or expired API key.
- `402`: The account has no balance, or a LIVE key was used before the first top-up.
- `403`: The API key lacks the permission this operation requires, or the account is suspended or closed.
- `404`: NOT_FOUND: no active consent for the email address.
- `422`: EMAIL_INVALID_ADDRESS.
- `429`: Rate limit reached: 100 requests per second per account, or a route-specific limit (Retry-After set where one applies).
- `500`: Unexpected server error.
- `501`: EMAIL_COMING_SOON: email consent is available when the email product launches.

---

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