The Movie Database Support
Support → API Support
"poster_path" and "genre_ids" are missing when searching by IMDB ID, but fine when searching by title.
posted by Freddy12STAFFMOD on October 15, 2019 at 4:59 AM
Hi,
seems like a bug.
The "poster_path" and "genre_ids" are show fine when searching by title (first result), but it's missing (null) when searching by IMDB id. For example:
https://api.themoviedb.org/3/find/tt7657364?api_key=YOUR_API_KEY&external_source=imdb_id
http://api.themoviedb.org/3/search/movie?api_key=YOUR_API_KEY&query=Gothic+Harvest&year=2018
The found result is the same movie (TMDB ID: 634775), but the "poster_path" and "genre_ids" are missing when searching by IMDB ID.
The "poster_path" and "genres" are also missing when just fetching information for that specific movie:
https://api.themoviedb.org/3/movie/634775?api_key=YOUR_API&language=en-US
Reply by Freddy12
on October 15, 2019 at 7:27 AM
It's now showing fine for that movie.
However there are other movies like that.
Is there some sort of delay depending on request (search) type?
That movie is quite old (from 2018) and the information was most likely added long time ago. Strange that info was missing in some requests.
Reply by ticao2 š§š· pt-BR
on October 15, 2019 at 1:01 PM
It is not a bug.
The two data you are looking for, Genres and Poster ID, were added by users today. (5 Posters and 1 Genre - Horror)
I don't know what time. Look here:
https://www.themoviedb.org/movie/634775-gothic-harvest/changes
I don't know what time you submitted your Requisition.
It may have been before or after this data was added.
But in addition, added data is not immediately available for API Requests.
In the past, API servers were updated every 8 hours.
Today I believe it will be in less time.
It even depends on the amount of new data sent.
Some things are almost immediate. Others take a little longer.
Reply by Freddy12
on October 15, 2019 at 1:39 PM
I see. If it was only added today then that's fine, I'm familiar that it's not available in API immediately.
I was more confused why the data was available in one request, but not in another request.
Now everything seems to be fine.
Will keep this in mind that it's normal :)
Thanks!