---
title: "Unsubscribe Get"
method: GET
path: "/email/unsubscribe/{token}"
tags: ["Atlas Email Marketing"]
---

# Unsubscribe Get

`GET /email/unsubscribe/{token}`

## Request

- Base URL: `https://app.atlasipholdingsllc.com` (the document declares no server; this is the origin it was published from)
- URL: `https://app.atlasipholdingsllc.com/email/unsubscribe/{token}`
- Auth: none declared

The footer link.

MARKETING mail links here without ?confirm, and this ACTS rather than showing a confirm button: some clients
and security scanners prefetch links, and the failure modes are not symmetric for marketing: honouring an
opt-out that a scanner triggered costs one address, while failing to honour a real one earns a spam complaint.

TRANSACTIONAL mail (receipts, verification, password resets) links here WITH ?confirm=1. That asymmetry does not
hold there: nobody is complaining about a receipt, and a scanner pre-fetching it must not unsubscribe the
customer. So confirm=1 only renders a button, and the button POSTs.

## Path parameters

- `token` string, required

## Query parameters

- `confirm` integer

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/atlasipholdingsllc/apis/atlas-data-exchange-api.md) · [All operations](https://skmtc.dev/atlasipholdingsllc/apis/atlas-data-exchange-api/llms.txt) · [OpenAPI document](https://skmtc.dev/atlasipholdingsllc/apis/atlas-data-exchange-api/revisions/153f570efc30?raw)