API endpoints returning unconventional error messages

[local_ip (jmk)]

Some API endpoints are returning errors as JSON strings (format sometimes used on BEDEV2) rather than the standard {"errors": [...]} object that we are used to on BEDEV1 endpoints.

This breaks the standards set in this post:

@Iron_Legion

Here are the upcoming standardized error responses. They will be gradually rolled out over the next few months, so your code may need to handle both the old and new responses for a few months.

This has caused API wrapper libraries and API consumers to break, as they assume that errors will be in this format.

[Iron_Legion]

Thanks for the report. We will look into this.

Are there any other cases you are noticing besides 429 “Too many requests” where you are receiving raw strings, instead of the expected JSON responses?

[local_ip (jmk)]

I’ve also seen "Challenge is required to authorize the request"

[Iron_Legion]

We’ve identified the problem and are working on a fix. It may take a few weeks to roll this out across the board.

[1mrpoorguy (MrPoorguy)]

the problem still persists when will it be fixed