Question

TwitchTracker API request

  • 28 November 2023
  • 6 replies
  • 726 views

TwitchTracker.com maintains up to date statistics for Twitch streamers, including useful data like follower count and average viewers. The site has an API that allows access to that data via a URL ending in the desired Twitch channel name: https://twitchtracker.com/api/channels/summary/[channelname]

When I check one of these URLs with an API checker like the one at https://reqbin.com/, it successfully returns the data I’m looking for. However when I try to do a GET request from Zapier on one of the above API URLs with an appropriate channel name filled in, it always returns “ "Forbidden" (HTTP Status Code: 403)“

I’m admittedly very rusty on my webhooks, and TwitchTracker has no documentation about their API, so the most likely explanation is that I’m missing something extremely fundamental.


This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

6 replies

Userlevel 7
Badge +14

Hi @TimG 

We would need to see detailed screenshots with how your Zap steps are configured to have more context.

Here’s the current baseline configuration of how the Zap is configured - I’ve tried some variations of the options, but always get the same result. Haven’t set any specific queries because I want to pull in the full data from the endpoint.

 

 

Userlevel 7
Badge +14

@TimG 

e.g. https://twitchtracker.com/api/channels/summary/ign

 

I was able to replicate your 403 error with the Webhooks Zap app.

 

When I tested with a Zap Code (JavaScript) step I got this error:

 

But when I tested with an Airtable Run Script (JavaScript) step in an Automation I got results:

 

So does this mean I’d need to use Airtable as an intermediary?

For context, what I’m attempting to do is pull this information into a Notion database, with records for certain channels.

Userlevel 7
Badge +14

@TimG 

From my initial testing looks like you could do this data logging/tracking/updating solely in Airtable.

If needed you could then use Zaps to move the data from Airtable to Notion.