You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: SpotifyAPI.Docs/docs/auth_introduction.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,16 +7,17 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
7
7
8
8
Spotify does not allow unauthorized access to the api. Thus, you need an access token to make requets. This access token can be gathered via multiple schemes, all following the OAuth2 spec. Since it's important to choose the correct scheme for your usecase, make sure you have a grasp of the following terminology/docs:
Since every auth flow also needs an application in the [spotify dashboard](https://developer.spotify.com/dashboard/), make sure you have the necessary values (like `Client Id` and `Client Secret`).
14
14
15
15
Then, continue with the docs of the specific auth flows:
// Redirect user to uri via your favorite web-server
40
+
// Redirect user to uri via your favorite web-server or open a local browser window
41
41
```
42
42
43
43
When the user is redirected to the generated uri, he will have to login with his spotify account and confirm, that your application wants to access his user data. Once confirmed, he will be redirect to `http://localhost:5000/callback` and a `code` parameter is attached to the query. The redirect URI can also contain a custom protocol paired with UWP App Custom Protocol handler. This received `code` has to be exchanged for an `access_token` and `refresh_token`:
@@ -47,23 +47,31 @@ When the user is redirected to the generated uri, he will have to login with his
47
47
publicTaskGetCallback(stringcode)
48
48
{
49
49
// Note that we use the verifier calculated above!
0 commit comments