I try to auth user with my app with spotify internet API however I get this error:

INVALID_CLIENT: Invalid redirect URIURL:

GET https://accounts.spotify.com/authorize/?client_id=6ae90bf75bf748c8874a75d16682f0c5&response_type=code&redirect_uri=https%3A%2F%2Fexample.com%2Fcallback&scope=user-read-private%20user-read-emailI cant view where is the problem... Can you help?



You have actually to include the redirect URI to the White-list in "My Applications" panel.

You are watching: Invalid_client: invalid redirect uri

e.g http://example.com/callback/



var redirect_uri = "http://localhost:8888/callback";(https://developer.spotify.com/dashboard) Spotify > my application:

http://localhost:8888/callbackDont forget come save.



I ran right into a comparable issue when authenticated via Authorization code Flow.

Per the docs The worth of this parameter have to exactly match the value of redirect_uri supplied once requesting the authorization code.So make sure that the:

redirect_uri that is configured in the dashboard

is exactly the exact same or else you will acquire a INVALID_CLIENT: Invalid redirect URI

Navigate to your Spotify developer dashboard and open the task you space working on.

Next click "edit settings" and look for the redirect URIs field.

Put your redirect URI in the field. Ex: http://localhost:8888/callback

Click save.

You should be good

First. You have to be sure that you"re making use of app.js indigenous authorization_code directory.

Second. Be certain you edited app.js. That 3rd line is important.

var client_id = "---"; // Your customer idvar client_secret = "---"; // her secretvar redirect_uri = "http://localhost:8888/callback"; // her redirect uri - EXAMPLE
I use the SpotifyAPI-NET API wrapper by JohnnyCrazy and was having actually this trouble despite including the URL I mentioned in mine wrapper contact to my white list as stated above.

The browser"s address bar should display the redirect URL that is using buried in the middle of the string - I found that the was likewise making a request through "https://accounts.spotify.com:8000/authorize" as the redirect URL - maybe the wrapper is do 2 API calls, yet I found that just by whitelisting both this URL and also the one ns was specifying would certainly it work for me.

This is at sight specific, so make certain you have specific url in each place.

In my application dashboard top top spotify ns had:http://localhost:3005/

And mine url is:https://accounts.spotify.com/authorize?client_id=XXXXXXXXXXXXXXXXX&response_type=code&redirect_uri=http%3A%2F%2Flocalhost:3005/&scope=user-read-currently-playing%20user-top-read

Note the trailing slash in both places.

This error also appears when the redirect_uri is lacking in the request. Ns figured that out the hard means due to writing "redirect_url" (with an L) instead.

Took me method too lengthy to number out. Hopefully this deserve to save who else part time.

+1 to adding "http://localhost:8888/callback" come the Redirect URIs perform in her App"s setups via https://developer.spotify.com/dashboard/applications

It"s a shame this is not pointed out on the quick start:https://developer.spotify.com/documentation/web-playback-sdk/quick-start/

incorporate a route after the very first pair of forward slashes. For example: Your application name is mine Awesome application The redirect URI might be my-awesome-app-login://callback or awesomeprotocol123://returnafterlogin.

See more: La Santa Muerte Oraciones Para El Amor, Book Libro La Santa Muerte Rituales Para

For an ext information please refer this link Spotify Redirect URI Example

I played around with assorted URLs for part time, none of them gave me the exactly functionality except http://localhost:8888/callback/ (note the rolling slash). Be certain to include that to the whitelist together well.

Highly active question. Knife 10 reputation (not count the combination bonus) in order to answer this question. The reputation requirement helps protect this question from spam and also non-answer activity.

Not the answer you're feather for? Browse various other questions tagged authentication spotify or ask your very own question.

site style / logo © 2021 ridge Exchange Inc; user contributions license is granted under cc by-sa. Rev2021.9.23.40291

her privacy

By click “Accept every cookies”, friend agree stack Exchange have the right to store cookies on your maker and disclose details in accordance with our Cookie Policy.