The process can be daunting at first, but there are several resources to help you.ĭocumentation is key! Luckily Spotify's Web API documentation was simple and easy to follow. (bars, beats, tempo, danceability, speechiness, etc.)įor a full list of Spotify API endpoints: Get a user's Playlists, Tracks, Albums, etc. Spotify Endpoints & Cool Stuff You Can Do With Them Manipulating the responses you get back however you'd like

update ( access_token: auth_params, refresh_token: auth_params ) endĦ - Accessing and Saving Real Spotify DataĮnsuring that you can save user data properlyįetching a user & their access token from our backend APIĮndpoint that the user has agreed to in the scopes of the initial authorization request #Update the user access/refresh_tokens if. Handling the 1-hour expiration for a user's Saving a user's access and refresh tokens

One of the more fragile and complicated pieces of this process. Here's a helpful article that explains how to hide your keys:ĥ - Create a UsersController to handle access and refresh tokens Scope is one of the more interesting parameters for this request. The component is the only thing being rendered on the page:Ĭonst SpotifyLogin = class extends React.Component ' end end How can I get it to redirect after authenticating?

Spotify reactjs