---
title: "Set the frequency cap"
method: PATCH
path: "/settings/frequency-cap"
tags: ["Usage"]
---

# Set the frequency cap

`PATCH /settings/frequency-cap`

## Request

- Base URL: `https://sending.dev/api/v1`
- URL: `https://sending.dev/api/v1/settings/frequency-cap`
- Auth: HTTP bearer

At most `max` MARKETING messages per contact every `days` days. Needed because no flow knows about the others: someone who joins a list on Monday, clicks on Tuesday and has an event during the week gets four emails in three days without anyone having decided it. Transactional messages are never held and do not count. Out-of-range values are clamped into the limits instead of being rejected. Required scope: `settings:write`.

## Request body

- FrequencyCapUpdate
  - `max` integer, nullable: Maximum marketing messages per contact in the window; `null` = no cap.
  - `days` integer: Window size in days (1-90).
  - `policy` 'skip' | 'defer': `skip` drops the excess message, `defer` postpones it until the window frees up.

## Response `200`

Cap updated.

- FrequencyCap
  - `max` integer, nullable, required: Maximum marketing messages per contact in the window; `null` = no cap.
  - `days` integer, required: Window size in days (1-90).
  - `policy` 'skip' | 'defer', required: `skip` drops the excess message, `defer` postpones it until the window frees up.

## Other responses

- `401`: Missing or invalid token.
- `403`: Insufficient scope.
- `422`: Invalid input.

---

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