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 by then? I have a couple apps sending JSONP requests and I’d really like to keep them healthy.

Look like its planned to be fixed, no ETA though: [image] Client-ID Requirement FAQs 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.

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

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

JSONP requests and the Client-ID requirement

API

george June 22, 2016, 9:59am 2

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

Topic		Replies	Views
Client-ID Requirement FAQs API	64	52648	October 23, 2016
API Stream Query API	8	5541	October 10, 2016
Kraken API stopped working when fetching streams API	7	2705	October 11, 2017
[Bug] Reworked /streams endpoint bugs out on client_id param API	7	1960	November 11, 2015
Use getJSON and sending client_id API	1	2462	January 28, 2014

JSONP requests and the Client-ID requirement

Related topics