Expected Behaviour: Examples should show the API in URL for making a request.
Actual Behaviour: API Key is shown in the authorization header in examples and running the example is causing a 401 error.
This issue is persisting in all the examples. Also, my authorization with a token is working fine without any issue.
The example code with node-:
const fetch = require('node-fetch');
const url = 'https://api.themoviedb.org/3/authentication';
const options = {
method: 'GET',
headers: {
accept: 'application/json',
Authorization: 'Bearer 2sdffsfsdeea43ba10423rt'
}
};
fetch(url, options)
.then(res => res.json())
.then(json => console.log(json))
Non riesci a trovare un film o una serie Tv? Accedi per crearlo.
Vuoi valutare o aggiungere quest'elemento a una lista?
Non sei un membro?
Risposta da brendonsreimer
il 12 ottobre, 2023 alle 3:08PM
Agreed. The documentation shows that you should include the API key in the authorization header, but that always fails with a 401. The request only works when you pass the API key through the URL. This is very confusing to the user.
Risposta da vvn123
il 12 ottobre, 2023 alle 4:35PM
If you are using API Key use it in the URL like this. Do not put it in the header.
Risposta da superboy97
il 13 ottobre, 2023 alle 2:06AM
The examples are wrong. As explained here, if you want to use the Authorization header, this is the Bearer token that you should put in it.