# JSONP requests and the Client-ID requirement

**URL:** <https://discuss.dev.twitch.com/t/jsonp-requests-and-the-client-id-requirement/6627>\
**Category:** API\
**Created:** [June 22, 2016, 6:36am UTC](https://discuss.dev.twitch.com/t/jsonp-requests-and-the-client-id-requirement/6627 "2016-06-22T06:36:40Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![pBun](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/pbun/32/1846_2.png) [@pBun](https://discuss.dev.twitch.com/u/pBun)\
**Post date:** [June 22, 2016, 6:36am UTC](https://discuss.dev.twitch.com/t/jsonp-requests-and-the-client-id-requirement/6627/1 "2016-06-22T06:36:40Z")

</div>

Will the `client_id` query string parameter satisfy the Client-ID August requirement for kraken api calls? Also, is there any chance of fixing [the `client_id` + `/kraken/streams` JSONP request issue](https://github.com/justintv/Twitch-API/issues/334) by then? I have a couple apps sending JSONP requests and I’d really like to keep them healthy.

---

<div class="post-metadata">

**Author:** ![george](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/george/32/120_2.png) [@george](https://discuss.dev.twitch.com/u/george)\
**Post date:** [June 22, 2016, 9:59am UTC](https://discuss.dev.twitch.com/t/jsonp-requests-and-the-client-id-requirement/6627/2 "2016-06-22T09:59:39Z")

</div>

Look like its planned to be fixed, no ETA though:

> [@Client-ID Requirement FAQs](https://discuss.dev.twitch.com/t/client-id-requirement-faqs/6108/19):
>
> We’re aware of the double usage of client\_id on streams endpoints and will be removing the filter parameter to address the issue. For now, sending the client id as a header won’t trigger the bug.

---

<div class="post-metadata">

**Author:** ![DallasNChains](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/dallasnchains/32/1608_2.png) [@DallasNChains](https://discuss.dev.twitch.com/u/DallasNChains)\
**Post date:** [June 22, 2016, 1:09pm UTC](https://discuss.dev.twitch.com/t/jsonp-requests-and-the-client-id-requirement/6627/3 "2016-06-22T13:09:33Z")

</div>

To answer your first question, yes. The query string parameter counts as stated in the FAQ.

---

<div class="post-metadata">

**Author:** ![pBun](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/pbun/32/1846_2.png) [@pBun](https://discuss.dev.twitch.com/u/pBun)\
**Post date:** [June 22, 2016, 10:20pm UTC](https://discuss.dev.twitch.com/t/jsonp-requests-and-the-client-id-requirement/6627/5 "2016-06-22T22:20:47Z")

</div>

Can’t believe I missed the FAQ. Thanks for the quick responses!

---

<div class="post-metadata">

**Author:** ![system](https://d2opxh93rbxzdn.cloudfront.net/original/2X/0/05909729875cce3b53e59d5561c4d23bb14948fc.png) [@system](https://discuss.dev.twitch.com/u/system)\
**Post date:** [July 22, 2016, 10:20pm UTC](https://discuss.dev.twitch.com/t/jsonp-requests-and-the-client-id-requirement/6627/6 "2016-07-22T22:20:56Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.