Hey!
I'm struggling to understand the purpose of some of the query parameters.
For instance, in /3/discover/movie
there's the primary_release_date
, then the gte
and lte
versions of release_date
, and then year
. And, when trying to get all movies of 2023, it only seems to work if I use both release_date.lte
and year
, but not just using one or the other, as one would expect.
Knowing the accepted values for some parameters isn't straightforward, either.
Is there any way I can find out more information about an API's query parameters?
Thanks!
Non riesci a trovare un film o una serie Tv? Accedi per crearlo.
Vuoi valutare o aggiungere quest'elemento a una lista?
Non sei un membro?
Risposta da ticao2 🇧🇷 pt-BR
il 28 giugno, 2023 alle 8:38AM
Primary Release Date versus Release Date
primary_release_date= is the date chosen by the TMDb system to be the official release date for a Movie. World Premiere.
This date determines the year that appears in parentheses next to the film's title on the film's page.
release_date= are all the release dates of a Movie in each and every country in the world, over time,
including premieres, festival, on television, in Bluray or DVD, digital media, etc ...
A movie can only have one primary_release_date
But it can have several and countless release_date
A different opening date for each country, for each media,
for open television, for cable TV, re-releases, 50th anniversary celebration, etc ... etc ... etc ...
Using "release_date=" and defining a "region=" you can filter by release dates in your country.
If you only want movies from a specific year just use "year" and you will get movies whose "primary_release_date" is from the year you are looking for.
But if you want movies from 2 different subsequent years, 2008 and 2009 for example, then you should use for example:
primary_release_date.gte=2008-01-01
primary_release_date.lte=2009-12-31
Risposta da Thecafremo
il 28 giugno, 2023 alle 3:45PM
Hey @ticao2 and thanks for clarifying these, it does help.
My concern, though, is that this information is not – as far as I know – within the official documentation so, when you using these endpoints, you have to assume what they are for, or the expected values.
Is this documented anywhere? Even if it's on a third party library that you're aware of? Are there any plans on updating the documentation to cover this?
Thanks!
Risposta da leanne63
il 28 giugno, 2023 alle 5:32PM
I have to add... I like many facets of the new documentation: the online queries work correctly now, for example. However, it does seem like some of the helpful details are now missing. I've had to go back to notes in my code to understand how to use some of the queries. Pros and cons, I guess...
And, I definitely appreciate the massive effort @TravisBell and the team had to undergo to get it all published when the old system went down without notice!!!
Risposta da ticao2 🇧🇷 pt-BR
il 28 giugno, 2023 alle 5:52PM
It's not in the new documentation.
It was in the old one. We migrated 1 or 2 months ago.
Not that I know of.
Only Administrator Travis Bell can respond. Let's wait for him to come by.
Risposta da thec0dec8ter
il 8 maggio, 2024 alle 9:08PM
Hey
I am going through the same struggle that @Thecafremo was going through. In
/3/discover/movie
I have no idea whether the integer values forwith_runtime.gte
andwith_runtime.lte
are supposed to represent seconds or minutes. I am guessing they take minute values. If they do, the results aren't as accurate as I would expect. For example, awith_runtime.lte
value of 107 returns Dune: Part Two in the results (has a runtime of 167m)Risposta da ticao2 🇧🇷 pt-BR
il 9 maggio, 2024 alle 6:58PM
Problems with API Request
In order for someone to help you with API Request questions,
it is critical that you post here the API Request you are sending to the TMDb server.
Remember to replace your Key with MY_KEY , YOUR_KEY , THE_KEY , or something like that.
Not the programming code/script you used to build the API Request.
But the API Request that is sent to the TMDb server.
Or the API Request you would like to send.
Risposta da ticao2 🇧🇷 pt-BR
il 9 maggio, 2024 alle 6:59PM
If the only parameter/filter used in your API Request was this, with_runtime.lte, then there is no error.
This is because all runtime values added in all translations/countries are considered.
And in this case, whoever entered data from Azerbaijan added 1h 45m, that is 105m.
https://www.themoviedb.org/movie/693134-dune-part-two/translations
There are some filters/parameters that can solve the problem.
But I don't know if you used any of them.