# Set email frequency

> Markdown version of https://docs.postlake.dev/api/patch-email-preferences . The canonical page for humans.
> PostLake is the social media API for AI agents: https://postlake.dev/llms.txt

`PATCH /v1/email-preferences`

Set how often the attention summary may arrive. `daily` sends at most once a day and only on days something is actually wrong; `weekly` gathers anything still unresolved into at most one email a week; `off` stops it entirely. There is deliberately no MCP tool for this: these emails are how a person learns a post did not go out, and an agent that could switch them off could hide a failure it caused.

## Request

Authenticate with a bearer API key. Agents calling over MCP authorise with OAuth instead and never handle the key.

```bash
curl -X PATCH https://api.postlake.dev/v1/email-preferences \
  -H "Authorization: Bearer $POSTLAKE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"digestFrequency":"…"}'
```

### Body

| Field | Type | Required | What it is |
| --- | --- | --- | --- |
| `digestFrequency` | string (off, weekly, daily) | Yes |  |


## Response

Updated preferences (`200`).



### Example

```json
"…"
```


## Calling this from an agent

Agents working over the hosted MCP server reach the same product through tools rather than REST, and authorise with OAuth so your API key is never pasted into a chat.

## Errors

Every failure uses one shape: a stable `type`, a granular `code`, the field at fault in `param`, and a plain-language `fix`. See https://docs.postlake.dev/errors.md .

Retries are safe: send the same `Idempotency-Key` and a call that already succeeded returns its original result rather than repeating it.

## Common questions

**Is it safe to retry this call?**

Yes. Send the same Idempotency-Key and a call that already succeeded returns its original result instead of repeating the work. That is what makes it safe to hand to an agent that retries on its own.

**What happens when it fails?**

You get one error shape: a stable type, a granular code you can branch on, the offending field in param, and a fix written so an agent can correct itself rather than stop. Full list on Errors and retries.

## Related

- [Export account data](https://docs.postlake.dev/api/get-account-export.md) `GET /v1/account/export`
- [Get audit log](https://docs.postlake.dev/api/get-audit.md) `GET /v1/audit`
- [Read email preferences](https://docs.postlake.dev/api/get-email-preferences.md) `GET /v1/email-preferences`
- [Get current account](https://docs.postlake.dev/api/get-me.md) `GET /v1/me`