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))
¿No encuentras una película o serie? Inicia sesión para crearla:
¿Quieres puntuar o añadir este elemento a una lista?
¿No eres miembro?
Contestado por brendonsreimer
el 12 de octubre de 2023 a las 15:08
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.
Contestado por vvn123
el 12 de octubre de 2023 a las 16:35
If you are using API Key use it in the URL like this. Do not put it in the header.
Contestado por superboy97
el 13 de octubre de 2023 a las 02:06
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.