@cryptoking said:

I am trying to get movie details and the API end point is return 403 error. I am trying from Postman. Getting same for past few days. What am I doing wrong?

GET https://api.themoviedb.org/3/movie/5?api_key=apikey&language=en-US

Here is the response:

403 ERROR

The request could not be satisfied.

---

Bad request. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.

---

Generated by cloudfront (CloudFront)
Request ID: IYvhiIiUPtcXzID8Rm4W86Mw-AsvB81k374iBJ88BmkhuPcpy_8EMA==

Are you trying to access the TMDb servers from Russia/Belarus ?
If yes, see below.

Regarding Russian-originated access to TMDb servers, here's what our Administrator Travis Bell said.
https://www.themoviedb.org/talk/625129f1a135330b929e29d6#62522f9456b9f700665f8cce

Hi everyone, please see our official post about this here:
https://blog.themoviedb.org/the-movie-database-suspends-access-from-russia-and-belarus-b6a1a96fb35b

The Movie Database Suspends Access From Russia and Belarus

No, I am in USA

When I try to do the same thing on tmdb website, I am getting this error in the console.

Access to XMLHttpRequest at 'https://z4vrpkijmodhwsxzc.stoplight-proxy.io/3/movie/5?api_key=apikey&language=en-US' from origin 'https://developers.themoviedb.org' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: Redirect is not allowed for a preflight request.

Is this redirect legit? Postman should not have this CORS issues.

@cryptoking said:
No, I am in USA

I made your API Request example in my browser.
https://api.themoviedb.org/3/movie/5?api_key=THE_KEY&language=pt-BR
I received all the data normally.
So maybe Postman is not making the exact same Request or some other parameter in Postman Request is not correct.
I'll add the word Postman to your topic title.
Maybe some Postman user here on the forum can help.

@cryptoking said:

When I try to do the same thing on tmdb website, I am getting this error in the console.

Access to XMLHttpRequest at 'https://z4vrpkijmodhwsxzc.stoplight-proxy.io/3/movie/5?api_key=apikey&language=en-US' from origin 'https://developers.themoviedb.org' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: Redirect is not allowed for a preflight request.

Is this redirect legit? Postman should not have this CORS issues.

You are probably sending your API Request directly from the Developers page.
https://developers.themoviedb.org/3/getting-started/introduction
Developers.themoviedb.org is hosted by https://stoplight.io/
And yes, he's in trouble.
This is the error response I get on developers.themoviedb:

Response    503 Service Unavailable  

Error: Network Error  
Check the developer tools console, it might have more information on the error.  
If you are using an Ad blocker, it is possible your Ad blocker is blocking the request.  

But if I use the URL directly in the browser I get the correct answer.
Copy the URL of the API Request and paste it into a new tab or window.

Travis Bell, the Manager, said (2021-01-15):
https://www.themoviedb.org/talk/600184fc6aa8e0004077e364?page=1#6001bbacbe4b36003d514ac3

Hi @ user,
I believe Stoplight has temporarily blocked the Try it out feature for our account
because too many people were using it as the source for their apps,
and not using api.themoviedb.org for some reason.
No timeline on getting it restored, but that's the problem.
Switch to use our proper production address, api.themoviedb.org.

And here (2021-06-04)
https://www.themoviedb.org/talk/60ba469218b75100785c163b#60ba6c76ffd44d0079eaa363

Hi @, indeed Stoplight has temporarily blocked the "Try it out" feature for our account
because too many people were using it as the source for their apps,
and not using api.themoviedb.org for some reason.
No timeline on getting it restored, but that's the problem.

Got it, I think I figured it out. I have a json body appended to the request. Anomaly of an interceptor I have. Thank you so much. All good now. Really appreciate your help.