Return to Question

A related, but critical, concern is that any error raised as the result of a JSONP API call needs to be JSON with a 200 status, not HTML. We covered this in this issue: API Suggestion: suppress http error code when jsonp is specified

A related, but critical, concern is that any error raised as the result of a JSONP API call needs to be JSON with a 200 status, not HTML. We covered this in this issue: API Suggestion: suppress http error code when jsonp is specified

Kevin, it is important that this issue gets attention

UPDATE:

I am being told that this is by design.

I could not disagree more.

The inconsistent 503 throttling issue aside, the API is JSON based. HTML errors serve no purpose in response to an API request.

Regardless of the whys, api.stackoverflow.com behaves as has come to be expected, while the others do not.

I encourage library and app developers to switch the target site for any test suites from api.stackoverflow.com to any other endpoint, especially for consecutive page requests to understand the purpose of this post.