Announcements

Response code Forbidden

Response code Forbidden

peterdb

Plan

Premium

Country

Belgium

Device

Windows desktop

Operating System

Windows 10

 

We integrated the Spotify Web API into our system. For approx 2 months everything was working fine until last week.

I see a lot of errors on the calls we do. E.g Get user's available devices api call give sometimes the response code 403 (Forbidden). Approx 10% of those calls result in this error response. 90% goes well.

This was not the case until a week ago.

Is there any reason for this?

I don't think the quota is exceeded. Our App Status is showing: "Granted quota extension"


Kind regards

Peter

 

Reply
6 Replies

Peter_Schorn

Does the http response body contain any data?

peterdb

No, only the text : Forbidden

Peter_Schorn

Ensure you're authorized for the required scopes.

peterdb

Yes I'm authorized, otherwise I would get Response code 401 (Unauthorized).

Here I'm receiving Response code 403 (Forbidden - The server understood the request, but is refusing to fulfill it.)

My application is running now for 3 months and before 2 weeks ago I did not get any errors.

Has Spotify changed something? Is there a restriction on the API calls?

ohej
In general 403's indicate that the action is not allowed for the specific user because the API call requires a Spotify Premium subscription.

All the Player APIs that controls playback has this documented in the API reference:
"If the user making the request is non-premium, a 403 FORBIDDEN response code will be returned."

If you can confirm and reproduce that a premium user is getting 403's when calling the Player APIs please provide more details about which API you're calling. You can also PM me your client ID and we can investigate it, but please verify that this isn't free vs premium issue first.

peterdb

Hi Ohej,

 

We use a Spotify Premium subscription, ohterwise none of the calls would work.

We use several APIs (Player API, Albums, Playlists, ...). The one most used is /v1/me/player/devices in Player API. This is called in our app every minute.

But I have also noticed the same 403 response with other API calls like /v1/me/player/ in Player API and some others.

P.S. I sended you a PM message with our client ID.

 

 

Suggested posts

Env: prod