api.badgr.io returning error 406 - "Not Acceptable" - "Could not find acceptable representation"

[alekwo]

Hi,
since about yesterday, when I try to query the Badgr API, I'm getting the below error (regardless if done from the integration platform, CURL, or the docs page https://api.badgr.io/docs/v2/😞

GET https://api.badgr.io/v2/badgeclasses/78JIhg8bTI6LbR3q5Vc_Zg/assertions?include_expired=false&include...

Error: response status is 406
{
"timestamp": "2023-08-22T07:47:06.154+00:00",
"status": 406,
"error": "Not Acceptable",
"message": "Could not find acceptable representation",
"path": "/v2/badgeclasses/78JIhg8bTI6LbR3q5Vc_Zg/assertions",
"traceId": "2bedd497-2e8e-4253-b4f5-eef2b2a9db75"
}

It doesn't matter if I use authenticated or anonymous calls, the response is the same.

Any idea what changed/happened and how to resolve this?

[volodymyrs]

Hi!

We had the same error from yesterday both from LMS and from Badgr web API. But everything works with JS request or Postman.

Looks like something was changed on the Badgr side.

To solve it I removed 

'Accept' => 'application/json',

from the request headers. 

[alekwo]

Thanks, indeed without the Accept header it works from CURL.

Unfortunately, Workato (that I use for integration) is automatically adding the Accept header... I can change it to XML but can't remove it. It seems I need to wait for the fix on the server side.

[DanielDuggan]

I use Zapier for my integrations and have also started seeing these errors.  I'm using the official Badgr app on Zapier, so there is no way to change the headers (if that is indeed required).  I guess Canvas needs to fix/revert the change or update their app on Zapier.

A proper communication from them would be nice also...

[alekwo · Accepted solution]

It seems that the problem is now fixed and the API works as usual.