Update campaign frequency cap
Replaces the team’s contact frequency cap using the revision you read; a changed revision answers 409. Send null for a window to remove its limit, or both null to remove the cap. Setting a limit requires the contact frequency caps beta and otherwise answers 403 feature_unavailable; removing the cap does not. Requires a team API key or a signed-in team owner or admin; project tokens answer 403. A message over the cap is skipped with frequency_cap_exceeded; a later sequence message stops that recipient’s remaining sequence. Settled skips are never retried when a cap changes.
API keys require campaigns:manage. Project tokens are not accepted.
Authorizations
Send your team API key or project token as Authorization: Bearer <token>. The credential must have the required permissions. Project tokens can access only their own project.
Body
Most campaign messages one phone number receives from the team in any rolling 24 hours, 1 to 50. null sets no 24-hour limit.
Accepted alternatives
Value constraints
1 <= x <= 50Most campaign messages one phone number receives from the team in any rolling 7 days, 1 to 200. null sets no 7-day limit. Must not be lower than maxPer24Hours.
Accepted alternatives
Value constraints
1 <= x <= 200The revision from your last read.
Value constraints
0 <= x <= 2147483646Response
Success
Structured data carried by this object.