I’m working with the TwitchLib package to pull entitlement data for specific games. The basic API functionality works fine since I can fetch stream information and check broadcaster status without issues.
I’m trying to use the entitlements endpoint to get drop information for games. When I attempt to call the GetDropsEntitlementsAsync function, I keep getting an error about invalid client credentials or token problems.
Here’s my current approach:
var gameData = await api.Helix.Games.GetGamesAsync(gameNames: new List<string> { "Valorant" });
var drops = await api.Helix.Entitlements.GetDropsEntitlementsAsync(gameId: gameData.Games.First().Id);
I also tried including my user ID as a parameter but that didn’t help. After reading the API docs, it seems like you might need special permissions or ownership to access this data.
When I check the drops page on Twitch directly, I can see all the campaign information I need. Is there a different endpoint or method I should be using to get this game drop data programmatically?
You’re misunderstanding what the entitlements endpoint actually does. I ran into this same issue on a project - this endpoint only shows drops users have already claimed, not active campaigns or available drops for games. Your auth error happens because you need proper OAuth with user consent, not just client credentials. But even with correct auth, you won’t get the campaign data from Twitch’s drops page. They keep that info private and don’t expose it through their public API. If you want actual campaign details like drop schedules or active promotions, you’ll need to find other approaches since Twitch doesn’t provide this data programmatically. The web interface uses internal APIs that third-party devs can’t access.
yeah, classic mistake - the drops endpoint requires an app access token, not a user token. other endpoints work fine with user tokens so it trips people up. register your app in the twitch dev console and use the client credentials flow.
The drops entitlements endpoint you are trying to use is specifically designed to fetch information about drops that users have already claimed. It does not provide details about ongoing campaigns or available drops. To access this data, you typically need the appropriate OAuth scopes, and it is most effective when querying for entitlements associated with your own user account or using an application-specific token with correct authorization.
As for the campaign details displayed on the Twitch drops page, these are not exposed through their public API; hence, you may need to consider alternative methods, such as user access tokens with the “user:read:email” scope, for earned drops based on authenticated users. Alternatively, approaches like scraping could be explored, but they come with associated risks and limitations regarding Twitch’s Terms of Service.
I encountered similar authentication issues while developing a drops tracker last year. It seems likely that your token scope may be incorrect rather than the credentials themselves. The GetDropsEntitlementsAsync function requires a user access token with specific scopes tailored for the entitlements endpoint. Ensure you’re applying a token that includes the necessary entitlements scope in your TwitchLib setup. However, be aware that this endpoint is somewhat limited; it primarily reveals entitlements that users have already claimed, not the current campaign information. If you seek comprehensive drops campaign details, you may find that the API does not provide this data, as Twitch limits access to campaign metadata for security and business reasons. Please verify your token setup and confirm that this endpoint meets your data requirements.
Had this exact problem building a drops tracker for our team. Twitch’s drops API is garbage - it doesn’t give you the campaign data you need.
The entitlements endpoint only shows drops users already claimed. No active campaigns, eligibility requirements, or schedules you see on the web.
After weeks of fighting this, I automated everything with Latenode. It monitors Twitch’s drops pages, pulls campaign data, tracks changes, and sends notifications when drops go live. Way better than wrestling with API limits.
My workflow checks multiple games hourly and updates our database with current campaigns. 10 minutes to set up, handles all the edge cases manual API calls miss.