Announcements

Help Wizard

Step 1

NEXT STEP

FAQs

Please see below the most popular frequently asked questions.

Loading article...

Loading faqs...

VIEW ALL

Ongoing Issues

Please see below the current ongoing issues which are under investigation.

Loading issue...

Loading ongoing issues...

VIEW ALL

Web console endpoint VS developper endpoint

Web console endpoint VS developper endpoint

- Free plan unless premium happen to be needed

- Belgium

- PC

- Windows 10


- While working for my company, one of the thing that we need to do is to correct songs' artist/title. For that, one of the possible ways would be to use Spotify api to search using our title/artist then among the top results take the one closest to what we have.


So I have been testing the "search" endpoint however I have found that while the actual research (https://open.spotify.com/search) and the api's web console do give me results, the real api endpoint when contacted via code or via Postman sometimes give me a return null for the exact same research with the same account, the same token and the same url.


On the web console :
https://api.spotify.com/v1/search?q=andersn%20bazr&type=track&market=BE&limit=10
 gives me some result (and the correct one is among them)
On my code/Postman :
https://api.spotify.com/v1/search?query=andersn+bazr&type=track&market=BE&offset=0&limit=10
 give me a return null.

 

The only differences between the two url are because the second one is the one present in the return after request. The real request is
https://api.spotify.com/v1/search?query=andersn%20bazr&type=track&market=BE&offset=0&limit=10
- "q" => "query"
- "%20" => "+"
- offest of 0 added


PS : I tried by changing my request with the modifications before sending, no difference.

 

Is it possible that the endpoint accessible for developpers are more limited than the actual web console/website endpoint ? And it only happen for some researchs "andern bazr" or "andersn - bazr".

 

I contacted the help service (the french one) via chat to ask but they were unable to answer so the only way I can get some clarification is either here or via Twitter ... 🙂

Reply
0 Replies

Suggested posts