Hi,
I noticed an issue with the Multi search endpoint: https://api.themoviedb.org/3/search/multi
It has a poster_path in the response object, but it's always null. When checking the Person search, the image can be found under profile_path instead of poster_path.
I was wondering if the backend can fix that by redirecting the Person profile_path as a poster_path in the Multi endpoint.
Thank you.
Não consegue encontrar um certo filme ou série? Inicie sessão e adicione-o.
Deseja classificar ou adicionar este item a uma lista?
Ainda não é um membro?
Resposta de Travis Bell
em 26 janeiro 2024 às 11:01 AM
Hi @gustavopeq, no, we cannot make a change like this.
Every media object returned across all of the many different endpoints are the same. Whether it's search, lists, popular, or trending, everything is consistent per media type.
You'll have to check which media type it is you're dealing with and template out accordingly. Note the
media_type
field that is returned so you can make that decision.Cheers.
Resposta de gustavopeq
em 26 janeiro 2024 às 5:39 PM
Understood... So when using this Multi endpoint, if I need to display the Person's profile picture, it's expected that I do an extra API call by the Person ID, to be able to get the profile_path right? Thanks @travisbell
Resposta de Travis Bell
em 26 janeiro 2024 às 6:06 PM
No. The
profile_path
field is returned as part of the object. Here's the response for a search of "Brad Pitt", notice the first response has aprofile_path
fieldRequest
Response
Resposta de gustavopeq
em 26 janeiro 2024 às 6:22 PM
Ohhh, so it does comes with the profile_path when the media_type is "person" I was using "Response 200 body" in https://developer.themoviedb.org/reference/search-multi , and it doesn't list the profile_path there, so I thought it didn't exist at all. That makes more sense... Thanks a lot @travisbell