Get streams by ID in curl is so long

[BarryCarlyon]

@rdomingue

I did the same in CURL with PHP. Trying to get the stream by the name gave me an error :" Bad Request [status] => 400 [message] => The parameter “id” was malformed: the value must match the regular expression /^[1]+$". So I did it with the stream _ID

V5 API is by ID not by Login.

Reference

https://api.twitch.tv/kraken/streams/<channel ID>

You need the channelID/userID for the user whom you are looking up.

@rdomingue

As you can see the curl calls are almost the same as the javascript one. But, the result is far to be the same. In javascript the answer is almost instantly, with the curl it tooks around 1 minute to get the answer.

As to the speed issues sounds like a problem with your Host/Server rather than anything else. I don’t see any latencty/long times here.

Your mileage will vary with teams end point, as it’s unofficial/unsupported/undocumented.

You are comparing the speed of client side with the speed of your server, which are two totally different systems to compare. (different types of firewall and methods of performing the lookup)

---

1. 0-9 ↩︎