---
title: "Unsubscribe a contact from a list"
method: POST
path: "/lists/{id}/unsubscribe"
tags: ["Marketing (experimental)"]
---

# Unsubscribe a contact from a list

`POST /lists/{id}/unsubscribe`

## Request

- Base URL: `https://api.oveyon.com/v1`
- URL: `https://api.oveyon.com/v1/lists/{id}/unsubscribe`
- Auth: HTTP bearer

EXPERIMENTAL — enabled account by account; without it every call answers 403 module_disabled. Scopes read:contacts / write:contacts. Reason `api`: the API can subscribe again someone the API removed. This never suppresses the address — transactional email keeps flowing.

## Path parameters

- `id` integer, required

## Request body

- MktUnsubscribeInput: The contact by `email` OR `id` (exactly one).
  - `email` string: The contact’s email, normalized as on POST /v1/contacts: only ASCII whitespace (space, TAB, LF, VT, FF, CR) is trimmed from the ends; a Unicode space at either end (NBSP, U+3000…) is 400 `invalid_email`. ASCII only: the Unicode spelling of a domain is 400 `invalid_email` with `reason: address_not_ascii` — the contact exists only in its xn-- form.
  - `id` integer

## Response `200`

Status on this list now

- MktUnsubscription
  - `contactId` integer, required
  - `listId` integer, required
  - `status` 'unsubscribed' | 'null', nullable, required: `null` when the contact was never on this list.
  - `changed` boolean, required

## Other responses

- `400`: bad_request (exactly one of email/id), invalid_email.
- `401`: Missing or invalid API key.
- `403`: module_disabled — the marketing module is not enabled on this account. Insufficient scope (`insufficient_scope`, with `required` and `have`), a scope the key holds but cannot use while its human-approval lock is on (`scope_blocked_by_approval_lock`, with `required` — approve:holds, write:send-policies, manage:webhooks, write:inbound, write:templates, write:surveys, write:domains, write:contacts), API key switched off by its owner in the panel (`key_disabled` — the key is valid; turn it back on or use another one, do not rotate), sending disabled, account suspended (`account_suspended`) or unknown (`account_unknown`), or the key used from an IP outside its allowed ranges (`ip_not_allowed`, with the `allowed` list — see /v1/credentials/ip-rules). 403 is not a limit: do not retry.
- `404`: list_not_found or contact_not_found.
- `413`: payload_too_large — the request body exceeds this route's limit (`limit`, in bytes: 25 MB unless the operation says otherwise). The key is validated before the body is read: without a valid key the answer is 401/403 and the body is not read. Do not retry the same body.
- `415`: unsupported_media_type — send the body as `application/json` (form and plain-text bodies are not accepted).
- `429`: Per-key limit (`rate_limited`, 600 requests/min by default per API key — or per MCP OAuth connection —, from any IP), per-IP limit for requests WITHOUT a valid credential (`rate_limited`, 600/min by default), too many unknown or malformed credentials from your address (`too_many_auth_failures`, 20/min by default, counted per IPv4 address or per IPv6 /48; a missing `Authorization`, an expired OAuth token or a disabled key do not count, and anything without the shape of one of our keys counts without being checked; from an address over that limit a valid key still gets through within 120 credential checks/min, and above them every credential not validated in the last 5 minutes gets this 429 until the minute turns) — all checked before the route, on every operation —, account quota (`quota_exceeded` with `window`, `used`, `limit`), warmup cap (`warmup_cap_reached`) or saturation (`queue_full`). Honor `Retry-After` with exponential backoff and jitter.
- `500`: internal_error — an unexpected failure on our side. The detail stays in our logs, never in the body. Retry reads; retry a write only when it is idempotent or carries an idempotency key.
- `503`: contact_busy — another request of this account kept writing to the same contact (or the same new tag) for a few seconds, and this one gave up instead of waiting longer. Nothing is wrong with the request: retry after `Retry-After` (5 s, also in `retryAfter`); retrying is safe. Or ip_rules_unavailable — the IP ranges bound to your key could not be checked right now (caution, not a denial; `Retry-After` 30 s).

---

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