Assuming you mean “making a call in the front end”, your first problem is to solve the authentication requirements. here is an example that uses implicit auth to log the user in first. Which put simply, is the safest way to obtain and use a users token. (You can return/use the users “normal” oAuth token, but that means you have a server doing the token exchange store and recall, and you shouldn’t leak an app access token on the front end)
The key part is line 28, using fetch to make the call.
If you don’t want to or can’t log the user in, or it’s not practical (to use implicit auth), then you make a fetch/ajax call from your front end to your backend, and the backend will use it’s app access token to make the call instead. (and cache the result to save extra API calls). Which would be the preferred method really.
TLDR: You need a server, so you probably won’t be making calls in the frontend to helix really at all
And if you are working with a known set of streamers you can implement Webhooks instead and make no API requests at all, (except to maintain your Webhooks)
https://dev.twitch.tv/docs/api/webhooks-guide
Ideally in this example, you’d authenticate the user on the server and store their keys in your database.
An authentication token gives you 800 API requests per minute (give or take) and with that you can look up 100 streams per request. So you can look up quite a lot of streams per minute if running at full speed
Rate limit docs:
Streams documentation
You can specify up to 100 user/userID’s per request