Some people appear to be inadvertently hitting our API endpoint instead of the proper server cluster. I haven't been able to track down a reason why as of yet.
They see the standard API error for hitting the endpoint with a malformed query, i.e.
{
success: false,
status: 500,
error: "You must target an API version.",
timestamp: 1373914539,
qcount: 0,
elapsed: "0.0257s"
}
I haven't been able to reproduce this issue locally yet. I'll continue to track the problem and update this issue as necessary.
evansims
commented
11 years ago
Some people appear to be inadvertently hitting our API endpoint instead of the proper server cluster. I haven't been able to track down a reason why as of yet.
They see the standard API error for hitting the endpoint with a malformed query, i.e.
I haven't been able to reproduce this issue locally yet. I'll continue to track the problem and update this issue as necessary.