We are currently integrating Twitch Drops for one of our games and have encountered an issue accessing the Drops Campaigns API.
Observed behavior:
Using the same Client ID and valid access tokens:
GET /helix/entitlements/drops returns 200 OK as expected
GET /helix/drops/campaigns consistently returns 404 Not Found
This occurs:
With both app access tokens and user access tokens
With or without game_id
When querying a specific campaign by id (campaign UUID)
Other Helix endpoints function normally with the same authentication headers.
Based on Twitch API behavior, this appears to indicate that the Drops Campaigns API may not be enabled or visible for our application, rather than an authentication or request formatting issue.
Could you please help confirm:
Whether access to the Drops Campaigns API requires additional enablement or whitelisting for our app
And if so, whether you can assist in enabling this capability for our Client ID
We are happy to provide any additional information you may need (Client ID, Game ID, request IDs, timestamps, etc.).
Just to add on to what Barry said about that API endpoint not existing at all which is why it 404’d, whitelisting to access Drops as an organization also doesn’t exist as you can see from the Drops Documentation. Once you’ve got an Organization within the TwitchDev console, and have successfully claimed game ownership, you can create Drops Campaigns, that’s all that’s required.