One-click unsubscribe (RFC 8058)

curl --request POST \
  --url https://api.member.dev/unsubscribe \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data 'List-Unsubscribe=<string>'

{
  "detail": [
    {
      "loc": [
        "<string>"
      ],
      "msg": "<string>",
      "type": "<string>",
      "ctx": {},
      "input": "<unknown>"
    }
  ]
}

email-unsubscribe

One-click unsubscribe (RFC 8058)

RFC 8058 one-click unsubscribe endpoint.

Mail clients (Gmail, Apple Mail) POST to this URL with the form body: List-Unsubscribe=One-Click

The JWT token is accepted from either:

t query parameter (standard form)
Implicit in the original t query parameter on the URL

Returns 200 with an EMPTY body on success. Gmail / Apple require either 200 or 204 with no body content.

Status codes: 200 — success (empty body) 400 — invalid or expired token (empty body)

POST

unsubscribe

One-click unsubscribe (RFC 8058)

curl --request POST \
  --url https://api.member.dev/unsubscribe \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data 'List-Unsubscribe=<string>'

{
  "detail": [
    {
      "loc": [
        "<string>"
      ],
      "msg": "<string>",
      "type": "<string>",
      "ctx": {},
      "input": "<unknown>"
    }
  ]
}

Authorizations

Authorization

string

header

required

Send platform JWTs, contact JWTs, or team API keys as Authorization: Bearer <token>.

Query Parameters

string | null

Signed unsubscribe JWT token.

Body

application/x-www-form-urlencoded

List-Unsubscribe

string | null

RFC 8058 form field; value should be 'One-Click'.

Response

Successful Response

Unsubscribe via link (browser)List email suppressions (platform-admin)

⌘I