Sign in
scheduled-notifications

Notification Tier Census

How many notification-eligible users fall into each taper tier.

Answers "what would happen if I turned tapering on", and with the query parameters, "what would happen at these thresholds instead" — so a threshold change can be costed before it is made rather than discovered afterwards.

DO NOT PUT THIS ON A CRON. Measured against production it takes ~90 seconds and sequentially scans daily_quests, because the activity expression is not indexable. It is deliberately on demand and deliberately not part of the nightly scheduling job. Expect it to be slow when you call it.

Reports tiers regardless of whether NOTIFICATION_TAPER_ENABLED is set.

Requires x-api-key header for authentication.

post/api/scheduled-notifications/admin/notification-tier-census

Query parameters

throttle_after_daysinteger nullable

Override the configured throttle threshold

Override the configured throttle threshold

pause_after_daysinteger nullable

Override the configured pause threshold

Override the configured pause threshold

Headers

x-api-keystring required

Response

Successful Response

{"stackTrail":"paths:/api/scheduled-notifications/admin/notification-tier-census:post:responses:200:content:application/json:schema","oasType":"schema","type":"unknown"}

Changes

Changed in 1 of the 14 revisions of this API.1