Register your game on Twitch as a category and obtain Twitch developer credentials; navigate to the Twitch Developer Console and ensure your organization is verified with Twitch (required for Drops).
In the Drops Campaign manager (accessible via the Twitch developer or partnership dashboard), create a campaign: set the game category, time window, and required watch minutes per drop.
Define Drop Benefit items (what players receive) and map them to Twitch Benefit IDs; provide a fulfillment webhook URL — Twitch will POST to this URL when a drop is claimed.
Implement the fulfillment webhook endpoint: Twitch sends a JSON payload with the Twitch user ID, benefit ID, and entitlement ID; respond with HTTP 200 within a few seconds or Twitch will retry.
In your webhook handler, map the Twitch user ID to a game account (store a Twitch-to-game account link from your OAuth flow), grant the in-game item, and record the entitlement ID to prevent duplicate fulfillment.
Mark entitlements as fulfilled by calling the Twitch Entitlements API (PATCH /entitlements) so the Twitch dashboard reflects completion status.
Known gotchas
Drops campaigns require Twitch partner or affiliate status for the streamer, and the game category on Twitch must match exactly — drops will not trigger on streams categorized under a different game name.
Twitch retries webhook delivery if your endpoint does not respond with 200 promptly; idempotently check the entitlement ID before granting rewards to avoid duplicate item grants on retry.
Users must connect their Twitch account to your game account for fulfillment to work; if no link exists when the drop fires, you must queue the entitlement and fulfill it when the user connects their account later.
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