The Movie Database 支持

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))

3 回复(第 1 页,共 1 页)

Jump to last post

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.

If you are using API Key use it in the URL like this. Do not put it in the header.

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.

找不到电影或节目?登录并创建它吧。

全站通用

s 聚焦到搜索栏
p 打开个人资料菜单
esc 关闭打开的窗口
? 打开键盘快捷键窗口

在媒体页面

b 返回(或返回上级)
e 进入编辑页面

在电视季页面

(右箭头)下一季
(左箭头)前一季

在电视集页面

(右箭头)下一集
(左箭头)上一集

在所有图像页面

a 打开添加图片窗口

在所有编辑页面

t 打开翻译选择器
ctrl+ s 提交

在讨论页面

n 创建新讨论
w 切换关注状态
p 设为公开 / 私密讨论
c 关闭 / 开放讨论
a 打开活动页
r 回复讨论
l 跳转至最新回复
ctrl+ enter 发送信息
(右箭头)下一页
(左箭头)前一页

设置

想给这个条目评分或将其添加到片单中?

登录

还不是会员?

注册加入社区