---
title: "Acts on current_user() only; takes no user id, so no resource-access decorator applies."
method: PUT
path: "/api/v1/prefs/marketing-emails"
tags: ["Lifecycle Email"]
---

# Acts on current_user() only; takes no user id, so no resource-access decorator applies.

`PUT /api/v1/prefs/marketing-emails`

## Request

- Base URL: `https://api.avatarfactory.io` (the document declares no server; this is the origin it was published from)
- URL: `https://api.avatarfactory.io/api/v1/prefs/marketing-emails`
- Auth: one of:
  - API key in cookie `session`
  - HTTP bearer

<br/>Turning emails back ON is a clear of the opt-out. If the stored reason is<br/>a vendor signal (`bounce` / `complaint` / `suppression`) rather than the<br/>user's own choice, the clear is refused with a 422: that address is<br/>known-bad and only support can re-enable it. A user-set opt-out (or any<br/>other reason) can always be cleared.

## Request body

- MarketingEmailsRequest
  - `enabled` boolean, required

## Response `200`

OK

- MarketingEmailsResponse
  - `enabled` boolean, required

## Other responses

- `401`: Unauthorized
- `422`: Unprocessable Entity

---

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