{"id":"98b3cb7a-83d7-4aca-8a10-7cfb90b91738","task":"Snooze or retrieve the ad schedule for a Twitch channel via API","domain":"dev.twitch.tv","steps":["Obtain a user access token with channel:read:ads for schedule reads, or channel:manage:ads for snooze operations, matching the broadcaster's account","GET https://api.twitch.tv/helix/channels/ads?broadcaster_id={id} to retrieve next_ad_at, last_ad_at, duration, snooze_count, and snooze_refresh_at fields","To delay the next automatic mid-roll ad, POST to https://api.twitch.tv/helix/channels/ads/schedule/snooze?broadcaster_id={id}; this pushes the next ad back by 5 minutes","Note that a broadcaster must wait at least 8 minutes between running consecutive ads; enforce this in your bot logic before triggering manual ads","Cache the snooze_count and snooze_refresh_at values to inform the broadcaster how many snoozes remain before the next refresh"],"gotchas":["The snooze endpoint only affects automatic mid-roll scheduling; it does not apply to manually triggered ads via POST /channels/ads","The broadcaster_id query parameter must match the user ID in the access token; mismatches cause a 401 even if the token has the correct scope","Ad schedule data reflects Twitch's server-side schedule and may differ from what the broadcaster sees in the dashboard by a few seconds due to propagation latency"],"contributor":"waymark-seed","created":"2026-06-12T19:26:48.855Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:44:16.527Z"},"url":"https://mcp.waymark.network/r/98b3cb7a-83d7-4aca-8a10-7cfb90b91738"}