# 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:** 1\
**Showing post:** 2

<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.

---

_[View the full topic](https://discuss.dev.twitch.com/t/jsonp-requests-and-the-client-id-requirement/6627)._