Unauthorized since update couple of days ago

I’m getting Unauthorized Responses back I’m sending requests to /api/missing , /api/qualityprofile
I do send an X-Api-Key with the apikey as header. Other calls seem to work, like /api/series , /api/calendar.

I know it should work because it did work, but after an update a couple of days ago. this problem just happend.

missing is now wanted/missing and qualityprofile is just profile - looks like the old redirects no longer work, we’ll take a look, but your calls should be updated (these were changed some time ago).

Yes it’s send from another app, but i didn’t change anything in the code of the app.
Even if i try to make a request with “Advanced REST Client” (an app from my chrome browser) i do get the same Unauthorized message.

It just appeard since a couple of days ago. So i assume that something did change on Sonarr’s side.

the url I’m send requests to are:

  • 192.168.1.108:8989/api/missing?page=1&pageSize=60&sortKey=airDateUtc&sortDir=desc
  • 192.168.1.108:8989/api/QualityProfile

with response:
{
error: “Unauthorized”
}

and if i send as example a request to:

  • 192.168.1.108:8989/api/series

I just get correctly the right json response.

all these requests are with an x-api-key: {apikey} as header.

Sorry, just updated my reply, I’ll take a look at the issue though.

I just saw the updated reply.

So for the missing episodes i do have to make a request to 192.168.1.108:8989/api/wanted/missing ?

profiles i just checked and i got that working.

Maybe it’s an idea to update the api doc directly after chancing something there, because the first thing I do is to check if the doc has been changed if something stopped working.

Updated now, but need to clean up missing a bit.

It changed months ago (and we forgfot to update the docs), but an authentication redirect in this update caused this one.

You’re probably the first person to have ever actually looked at them when it broke, most people don’t bother.

EDIT: pushing a fix to develop now.