Heads up! We’re going to require the Client-ID header along with your API requests as of August 8th. Thus far, it has been a soft requirement, but we’re going to start enforcing it. More details on the blog .

Thanks for the heads up. Is there any way to test that I am sending the headers correctly? I am working with Java.

The API doesn’t send back anything in particular to let you know. The best way to test this is to examine your network traffic (using DevTools, Fiddler, or equivalent) to ensure the headers are being sent.

Will it also work by suffixing the get-url with the client id, like it does today with token? Example: https://api.twitch.tv/kraken/channels/channelname/subscriptions?oauth_token=XXXXXX&client_id=XXXX

Yes , though it will be useless for GET /streams, where it has a different meaning (unless that changes).

You can now check if you’re properly identifying by pulling https://api.twitch.tv/kraken with your client ID specified. If properly identified, the identified field will return true.

Thanks for that @night ! I was just going to make a post about it. :slight_smile:

Is the clientID I get for my “App” safe to commit to a public repository on github?

Displaying the ClientID shouldn’t be to dangerous, as long as you keep your Client Secret confidential.

I assume this is a way for you to “track” API requests, is there any plan on adding a query per minute limit on requests too? (or is there one already?)

Do you mean a rate limit on API requests? Currently, if you don’t include Client-ID, you’re subject to rate limiting. See the rate limits section here .

Client-ID will be required in August

API

DallasNChains June 4, 2016, 12:54am 15

You’re sending the request to kraken/users. It should be just the root kraken as shown in the FAQ here: Client-ID Requirement FAQs

Topic		Replies	Views
Client-ID Requirement FAQs API	66	52247	November 22, 2016
Problem with Client ID API	5	1344	July 21, 2016
My App Access token is not working API	2	478	February 26, 2021
Client-ID identification: unexpected behaviour (v3) API	2	1105	December 28, 2016
V5 requires client-id with auth token? API	11	3726	December 28, 2016

Client-ID will be required in August

Related topics