Im getting this error
<NSHTTPURLResponse: 0x111459ac0> { URL: https://api.themoviedb.org/3/authentication } { Status Code: 401, Headers {
"Alt-Svc" = (
"h3=\":443\"; ma=86400"
);
"Cache-Control" = (
"public, max-age=300"
);
"Content-Type" = (
"application/json; charset=utf-8"
);
Date = (
"Fri, 21 Jul 2023 01:00:31 GMT"
);
Server = (
openresty
);
Vary = (
Origin
);
Via = (
"1.1 df49d0a48eba3cccd76163f6490dc2ce.cloudfront.net (CloudFront)"
);
"x-amz-cf-id" = (
"Ktf4uX5s1YWrK6369dMHKaUBD_3ObhooXAbtvWj-cGm4grcIbAa1gg=="
);
"x-amz-cf-pop" = (
"QRO51-P3"
);
"x-cache" = (
"Error from cloudfront"
);
} }
찾으시는 영화나 TV 프로그램이 없나요? 로그인 하셔서 직접 만들어주세요.
이 항목을 평가하거나 목록에 추가할까요?
회원이 아닌가요?
ticao2 🇧🇷 pt-BR님의 댓글
7월 21, 2023 at 8:11 오전
Can you tell us which of these errors is occurring?
See the list of TMDb server error warnings here.
https://www.themoviedb.org/documentation/api/status-codes
In your case:
richard_isai님의 댓글
7월 21, 2023 at 11:24 오전
This one: 7 401 Invalid API key: You must be granted a valid key.
Im using the same key as always
ticao2 🇧🇷 pt-BR님의 댓글
7월 21, 2023 at 11:53 오전
I don't really know how the TOKEN process works.
But I think you need to send the "Access Token Auth" and not the "API Key Auth".
Look here:
https://developer.themoviedb.org/reference/intro/authentication
But it's better to wait for someone who knows the process.
richard_isai님의 댓글
7월 21, 2023 at 11:59 오전
In using the same Access Token Auth as always
robbie3999님의 댓글
7월 21, 2023 at 12:56 오후
Hi @richard_isai, this response from the server would indicate that you are sending the wrong api key or token or not sending one at all.
You would need to send the api key as: https://api.themoviedb.org/3/authentication?api_key=xxxxxxxxxx
or, send the token in the header as "Authorization: Bearer xxxxxxxxxxxxxxxxx".
From the authentication doc, the key and token are two distinct and separate things and you must use the key in the url and the token in the authorization header.