Skip to main content
See also: Frequency Caps concept and configuration for what this API powers, when to call it, and how it is configured.

Overview

Frequency caps limit how many recommendations or deliveries can occur within a time period. They operate at three scopes:
  • Channel: Max emails/day, max push notifications/week
  • Category: Max mandatory communications/week
  • Offer: Max deliveries of a specific offer/month

List Frequency Caps

Returns all frequency caps for the tenant, ordered by creation date (newest first).

Response


Create Frequency Cap

Request Body

Example

Response 201

Returns the created cap. The currentCount starts at 0 and resetAt is auto-computed based on the period.

Error codes


Update Frequency Cap

Update an existing cap. Include id in the body. Only provided fields are updated.

Request Body

Changing the period automatically resets the currentCount to 0 and recomputes the resetAt timestamp.

Response 200

Returns the updated cap.

Error codes


Delete Frequency Cap

Query Parameters

Response 204

Empty body on success.

Error codes


How Frequency Caps Work

  1. When a batch run executes, each delivery increments the currentCount for matching caps.
  2. If currentCount >= maxVolume, further deliveries for that scope are blocked.
  3. Counters reset automatically at the start of each period:
    • daily: Midnight UTC
    • weekly: Monday midnight UTC
    • monthly: First day of the month, midnight UTC
  4. Frequency caps are checked AFTER qualification and contact policy filtering.

Role requirements


Example: Insurance Email Campaign