I’m trying to work with both Twitch’s newer API and the old V5 API. The V5 version gives me some extra channel data that I need for my project.
When I grab the token directly from my browser’s developer tools, everything works fine with both APIs. But when I use the token I get through Omniauth authentication, I keep getting this error: {"error":"Gone","status":410,"message":"It's time to kick ass and serve v3... and I'm all outta v3"}
I noticed that the Helix API uses Bearer tokens while the Kraken API uses OAuth tokens. How do I get the right OAuth token after a user logs in so I can access the V5 endpoints?
The browser token works with both API versions, but my Omniauth token only works with the new API.
UPDATE: Fixed it! You can use the same access token for both APIs. Just add the Accept header application/vnd.twitchtv.v5+json to your requests when calling V5 endpoints.
Nice catch on the header fix! I’ve hit similar API headaches where auth works but you’re hitting wrong endpoints.
Here’s what I’d do - skip juggling both APIs manually and set up automation that handles token management and API switching for you. Create a workflow that detects which data you need, grabs it from the right API version, and consolidates everything cleanly.
I built something similar for a streaming dashboard needing user data from multiple endpoints. The workflow handles OAuth, manages token refresh, sets headers automatically, and falls back to Helix when V5 data isn’t available.
You won’t worry about headers, rate limits, or API deprecation - just focus on using the data. Plus you can easily add webhook triggers when channel data changes.
Check out the automation options at https://latenode.com
glad you figured it out! that accept header is crucial for v5. just heads up tho - twitch has been pushing people away from kraken for a while now, so u might want to start migrating whatever data u need to helix endpoints when possible.
Been there with a stream analytics tool. Twitch’s docs make it seem like you need different tokens, but it’s really just about headers. Your Accept header fix is right on.
Watch out for rate limits if you’re hitting both APIs at once - I’d cache responses for frequent calls. Also check your Omniauth scopes for V5. Some older endpoints need permissions that aren’t in default configs.