---
title: "Unsubscribe an address from offers and announcements"
method: GET
path: "/v1/marketing/unsubscribe"
tags: ["Billing"]
---

# Unsubscribe an address from offers and announcements

`GET /v1/marketing/unsubscribe`

## Request

- Base URL: `https://api.1claw.co`
- URL: `https://api.1claw.co/v1/marketing/unsubscribe`
- Auth: none required

Public and session-less by necessity: the link lives in an email, and an unsubscribe that asks the reader to log in first is one they abandon — they mark the next message as spam instead, which costs the sending domain far more. The `t` parameter is an HMAC over the address, which is what stops a stranger unsubscribing somebody else.

Offers and announcements only. Transactional mail — sign-in codes, approval requests, invitations, reports the recipient asked for — does not consult this flag and is unaffected; turning it off must never lock someone out of their account.

Idempotent, and the answer is the same whether or not the address has an account. "Stop emailing me" is always answered "done", and a 404 here would tell a caller holding a valid token which addresses are registered.

## Query parameters

- `email` string, email, required
- `t` string, required
- `c` string

## Response `200`

Unsubscribed (or already was)

- object
  - `unsubscribed` boolean, required
  - `email` string, required
  - `message` string, required

## Other responses

- `400`: The link's signature did not verify

---

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