Trigger a Twitch raid from a chatbot and confirm it actually started via EventSub before crediting the raiding channel
domain: dev.twitch.tv · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
POST to the Start a raid endpoint with from_broadcaster_id and to_broadcaster_id to queue the raid
Note that this call only opens the in-UX raid confirmation window; it doesn't start the raid itself
Subscribe to the Channel Raid EventSub subscription type to learn whether the broadcaster actually clicked Raid Now or let the 90-second countdown expire
Match the from/to broadcaster IDs in the EventSub payload against your original request to confirm it's your raid before taking action
Send a DELETE to the Cancel a raid endpoint with broadcaster_id if you need to abort before the countdown ends
Known gotchas
The Start a raid response only confirms the request was queued (returns is_mature and created_at) — it is not confirmation the raid happened, which is why the Channel Raid EventSub subscription is required for anything depending on the raid completing
Canceling only works up until the broadcaster clicks Raid Now or the 90-second countdown expires; after that, Cancel a raid returns 404 Not Found instead of succeeding
The raid pop-up also implicitly surfaces subscriber-only/follower-only chat mode to viewers — a custom raid UI should pull that from Get Chat Settings' subscriber_mode/follower_mode fields rather than assuming default open chat
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?