The Client Credentials flow is used in server-to-server authentication. Since this flow does not include authorization, only endpoints that do not access user information can be accessed.
The following diagram shows how the Client Credentials Flow works:
Pre-requisitesThis guide assumes that:
You can find an example app implementing Client Credentials flow on GitHub in the web-api-examples repository.
The first step is to send a POST
request to the /api/token
endpoint of the Spotify OAuth 2.0 Service with the following parameters encoded in application/x-www-form-urlencoded
:
client_credentials
.
The headers of the request must contain the following parameters:
Header Parameter Relevance Value Authorization Required Base 64 encoded string that contains the client ID and client secret key. The field must have the format:Authorization: Basic <base64 encoded client_id:client_secret>
Content-Type Required Set to application/x-www-form-urlencoded
.
The following JavaScript creates and sends an authorization request:
_19
var client_id = 'CLIENT_ID';
_19
var client_secret = 'CLIENT_SECRET';
_19
url: 'https://accounts.spotify.com/api/token',
_19
'Authorization': 'Basic ' + (new Buffer.from(client_id + ':' + client_secret).toString('base64'))
_19
grant_type: 'client_credentials'
_19
request.post(authOptions, function(error, response, body) {
_19
if (!error && response.statusCode === 200) {
_19
var token = body.access_token;
Response
If everything goes well, you'll receive a response with a 200 OK
status and the following JSON data in the response body:
For example:
_10
"access_token": "NgCXRKc...MzYjw",
_10
"token_type": "bearer",
What's next?
Learn how to use an access token to fetch data from the Spotify Web API by reading the access token guide.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4