The Movie Database Support
Support → API Support
Cannot fetch translation info for a Movie using API, although it works in a browser
posted by mgruberSTAFFMOD on October 17, 2012 at 3:52 PM
When I request information for this specific Movie:
http://api.themoviedb.org/3/movie/57800?api_key=<my_api_key>&language=pt
I receive a summarized response from the english translation instead of portuguese.
On the other hand, if you open http://www.themoviedb.org/movie/57800-ice-age-continental-drift and switch to Portuguese, fields like title and overview are correctly translated.
Why is my API request failing?
Reply by Travis Bell
on October 17, 2012 at 4:04 PM
I deleted the cached entry and it's working now.
I can't speak to exactly why this happened, but I do have a theory. I am betting the original request was requested with the language params as an uppercase value (PT vs. pt). I'll push a fix for this today.
Thanks for letting me know.
Reply by mgruber
on October 17, 2012 at 4:12 PM
Yes, I guess you are right. I was trying the API and my first attempt I used 'PT' instead of 'pt'.
Reply by sodd
on December 23, 2012 at 2:53 PM
Hi, i have the same truble as mgruber.
When i send request like this:
http://api.themoviedb.org/3/movie/48231?api_key=&language=cs
I get overview:NULL etc. here is the list of my "fail" video reqest with Name and ID:
A dangerous method 48231 Baraka 14002 Basic instinct 402 Blood and bone 22164 Caligula 9453 Cyrus 39053 Elektra luxx 56272 Enchanted 4523 Stistko 1888 Good luck chuck 10030 hesher 44835 I love you phillip morris 8952 I sell the dead 21910 jeremiah 33201 the man with the iron fists 97430 my name is bruce 1961 No country for old men 6977 pontypool 23963 tengoku to jigoku 12493 the war of the roses 249 whats eating gilbert grape 1587 The words 83686 youth in revolt 22327 suspect x 42341
Reply by Travis Bell
on December 26, 2012 at 1:22 PM
Keep in mind the API caches responses, and with most of these I see the CS information was added the same day you made the requests. I just checked these and it looks like the cached response has been cleared and is now returning the updated data.