Skip to content

Unsubscribe (RFC 8058 one-click) โ€‹

POST /v1/public/email/unsubscribe

  • Operation ID: unsubscribeEmailOneClick
  • Tags: Email unsubscribe
  • Base URL: http://localhost:8787

Target of the List-Unsubscribe-Post header: mail clients POST List-Unsubscribe=One-Click to the same URL, with the token in the query string. The request body is not read. Records an unsubscribe with reason one-click.

Workflow: Integration guide.

Authentication: none (public).

Rate limit: 30 requests per 60s per ip.

Authentication โ€‹

  • Auth: none (public endpoint, no token required).

Rate limit โ€‹

30 requests per 60 seconds per ip. Exceeding it returns 429.

Parameters โ€‹

NameInTypeRequiredDescription
tokenquerystringyesMin length: 10. Max length: 2000

Responses โ€‹

200 โ€‹

Unsubscribed.

  • Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object

FieldTypeRequiredDescription
okbooleanyesOne of: true

Errors โ€‹

400 โ€‹

Request validation failed. validation_failed with details.token = "invalid": the token is malformed, tampered or expired.

  • Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object (ValidationErrorBody) | object (ErrorBody)

FieldTypeRequiredDescription
(variant 1).successbooleanyesOne of: false
(variant 1).errorobjectyes-
(variant 1).error.namestringyesOne of: "ZodError"
(variant 1).error.issuesobject[]yes-
(variant 1).error.issues[].codestringyes-
(variant 1).error.issues[].path(string | number)[]yes-
(variant 1).error.issues[].messagestringyes-
(variant 2).errorstringyesStable machine-readable error code, e.g. forbidden, not_found.
(variant 2).detailsanynoOptional structured context. For 403 it is { perm }.

Request validation

json
{
  "success": false,
  "error": {
    "name": "ZodError",
    "issues": [
      {
        "code": "custom",
        "path": [
          "field"
        ],
        "message": "Invalid value"
      }
    ]
  }
}

Application error

json
{
  "error": "validation_failed"
}

429 โ€‹

Rate limit exceeded (rate_limited).

  • Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object (ErrorBody)

FieldTypeRequiredDescription
errorstringyesStable machine-readable error code, e.g. forbidden, not_found.
detailsanynoOptional structured context. For 403 it is { perm }.

Error response

json
{
  "error": "rate_limited"
}

500 โ€‹

Unexpected server error (internal). No details are returned.

  • Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object (ErrorBody), fields as described above.

Error response

json
{
  "error": "internal"
}

503 โ€‹

Maintenance can refuse this write before authentication (degraded blocks session start and checkout; lockdown blocks other public/user writes).

  • Header x-request-id: Request identifier; quote it when reporting an error.
  • Header Retry-After: Maintenance retry delay in seconds; present for panic_mode. Example: 30. Content type: application/json

Schema: object (MaintenanceErrorBody)

FieldTypeRequiredDescription
errorstringyesOne of: "panic_mode"
levelstringyesOne of: "degraded", "lockdown"
reasonstring | nullyes-

Maintenance lockdown

json
{
  "error": "panic_mode",
  "level": "lockdown",
  "reason": "Scheduled maintenance"
}

Examples โ€‹

curl โ€‹

bash
curl -X POST 'http://localhost:8787/v1/public/email/unsubscribe?token=example000'

TypeScript โ€‹

ts
const response = await fetch("http://localhost:8787/v1/public/email/unsubscribe?token=example000", {
  method: "POST",
});
if (!response.ok) throw new Error(`HTTP ${response.status}: ${await response.text()}`);
const data = response.status === 204 || response.status === 205
  ? undefined
  : response.headers.get("content-type")?.includes("json")
    ? await response.json()
    : await response.text();

Try this endpoint

Requests go directly from your browser to the API. Send request executes this endpoint against the selected server.

POST/v1/public/email/unsubscribe

Your token stays in this tab's memory and is sent only when you press Send request.

Parameters

Built for developers. Ready for agents.