In the Twitch developer console, ensure your game is registered and your organization has the Drops feature enabled; if not, apply through the Twitch partner/developer program.
Create a Drops campaign in the Twitch console: define the campaign window, select the game category, configure required watch time per drop, and add drop benefits with preview images.
Set up a fulfillment webhook URL in the campaign configuration; Twitch will POST a notification to this URL when a viewer earns a drop, including the user's Twitch ID and benefit ID.
In your fulfillment webhook handler, verify the request signature using the Twitch-provided secret (HMAC of the message ID, timestamp, and body), then grant the corresponding in-game item to the player.
Link Twitch accounts to game accounts in your title's account system using the Twitch OAuth flow so you can map Twitch user IDs to your player IDs at fulfillment time.
Use the Drops API endpoints to query campaign status and fulfillment state, and to allow players to claim unclaimed drops from within your game client.
Known gotchas
Drops fulfillment is asynchronous; viewers earn drops passively and may claim them hours after earning — your fulfillment endpoint must be idempotent since Twitch may retry deliveries.
If a viewer has not linked their Twitch account to your game account before claiming, you cannot fulfill the drop; design a clear account-linking flow and queue unfulfilled drops for later delivery.
Campaigns require Twitch approval before going live; submit the campaign for review well ahead of the intended start date to avoid delays from the review process.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp