Client-ID identification: unexpected behaviour (v3)

As we know, a response from contains identified field to check if your client-id is valid. So, when I make such request with a valid client-id, I get identified: true.

But with invalid client-id I get this:
{"error":"Bad Request","status":400,"message":"No client id specified"}
however it should be identified: false

So… is it a bug?

No, this isn’t a bug. We added identified as a way to test before we required a Client-ID. Now that we require a Client-ID, the proper response is a 400 and no body returned.

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