I’m trying to build a feature that pulls the most viewed clips from Twitch based on specific regions or countries. I found some documentation for an older version of their API that had exactly what I needed, but it looks like that version is no longer supported.
When I check the current API documentation, I can’t seem to find a similar endpoint that lets me filter clips by geographic location. Has anyone worked with this recently? Is there a way to get region-specific popular clips using the newer API version?
I’m also wondering if it’s worth using the older deprecated endpoint as a temporary solution, or if that could cause problems down the road. Any advice on the best approach would be really helpful.
yup, twitch removed that geo-filtering in the new api, kinda sucks. no real way around it, honestly. using old endpoints isn’t a good idea, they could stop working anytime. maybe just fetch popular clips and filter by timezone or lang on your end.
Hit this same problem six months back building something similar. Yeah, they killed geographic filtering when they moved to Helix API - super annoying since Kraken made it dead simple. Here’s what worked for me: pull clips through the standard endpoints, then cross-reference streamer data to get roughly regional content. You can filter clips from streamers who mainly broadcast in specific languages or during time windows that match regional peak hours. Not perfect, but gets you close enough. Don’t touch the deprecated endpoints - Twitch’s been ruthless about killing those with zero warning. More work on your end processing-wise, but way more reliable.
Had the same problem when Helix API launched. No geographic filtering was a real pain for my project. I ended up digging into streamer data and viewership patterns to guess regional content. Checking clip timestamps helped me figure out peak viewing times for different regions - worked as a decent workaround. Language settings can give you some targeting hints too, though they’re not always reliable. Just avoid deprecated endpoints - learned that the hard way when they yanked them without warning.
honestly this is frustrating af, ran into the exact same wall last year. what i did was pull clips via game category then look at streamer profiles to see their usual streaming hours - that gives you a rough idea of their timezone/region. not perfect but better than nothing. definitely dont use old api endpoints tho, thats asking for trouble
Been dealing with this for over a year - it’s one of the most annoying changes Twitch made during the API transition. My workaround combines multiple data points. I fetch popular clips normally, then analyze chat language patterns and streamer metadata to figure out regional relevance. Another decent approach is checking follower demographics when available and cross-referencing with typical streaming schedules. The time zone analysis others mentioned works well but needs more processing power. You could also target specific game categories that are popular in certain regions. It’s way more complex than the old system but gives reasonable results if you’re willing to do the extra processing.