If I remember correctly.
A festival date, or Premiere, is only considered as primary_release_date while there is no Theatrical date.
When a Theatrical date appears, then that date will be the date considered primary_release_date.
And I assume the lists use primary_release_date.

EDIT:
See, for example, the movie Green Book (2018)
https://www.themoviedb.org/movie/490132-green-book/edit?active_nav_item=release_information
Has a Premiere date: 2018-11-09
But the primary_release_date is: 2018-11-16
It is the smallest Theatrical date.

Or the movie Dunkirk (2017)
https://www.themoviedb.org/movie/374720-dunkirk/edit?active_nav_item=release_information
It has a Premiere date: 2017-07-13 (London)
But the primary_release_date is: 2017-07-19

EDIT 2:
That is why, sometimes, the Year in TMDb is different from Year in IMDB.
The IMDB considers the first date, being it may be Premiere or Festival.
TMDb considers the first Theatrical date.
And sometimes, the date of the Festival and the date in the movie theaters are in different years.

No on the list I have I have movies like Long Shot and Shazam on there. Both of them have a Theatrical date in the system, but when I get the details of the list using https://api.themoviedb.org/3/list/{list_id}?api_key=<>&language=en-US It is giving me dates in the past (which neither have had their Theatrical release yet) . It'd be great if I could add &with_release_type=3 to that call to have it show the Theatrical date and not the Premiere one

I assume the two films you're referring to are these two:
https://www.themoviedb.org/movie/459992-long-shot
https://www.themoviedb.org/movie/287947-shazam
I'll look at the data from the two films and come back here.

Yes those are the ones that's stood out the most since they showed up as already released, but pretty sure it was looking at the Premiere date on all the ones in my list even tho they had Theatrical releases set if I did a discover call on them.

Long Shot (2019)
https://www.themoviedb.org/movie/459992-long-shot/edit?active_nav_item=release_information
The first Theatrical date is in South Africa: 2019-02-08

Shazam! (2019)
https://www.themoviedb.org/movie/287947-shazam/edit?active_nav_item=release_information
The first Theatrical (limited) date is in the USA: 2019-03-23

Are the dates considered as primary_release_date.
Are not these the dates that are in the details of your list?

But as I mentioned what I wanted was to be able to set it to Theatrical(3) and not a limited release and I guess I'd need region as well since it's looking at South Africa. I guess my issue is List are nice to have, but the current implementation is too limited to be useful for me.

It looks like setting region does work, which get me so close to where I need to to be. 😩

I still do not quite understand what you're doing.
But I'll assume you're making a get/discover/movie request and then, with the result, you're creating a list.
If this is what you are doing, then you can do this get/discover/movie request with the required region and release dates filters.

Sorry, let me explain, so I am working on an App that uses the discover call to return all the movies in a region that is going out in the next year and it looks is looking at release type 3 to display the number of days until that movie will be available for the users to see.

I also wanted to create a curated list as well that the user can switch to in the case they are overwhelmed by all the movies return by the discover call. But since with the list call it doesn't allow me to se the release type to 3 it is showing a different number of days until the movies are out. Which would confuse the users.

Hope that helps clarify things.

Hi @brianminor,

There is no option to set your desired release type on lists, but region does work, which gets you almost there.

v3 and v4 lists do use some of discover behind the scenes but the params passed back are currently restricted. I am not totally sure on how much work it would be to enable with_release_type without digging into it.

Here's the ticket I just created that you can follow or vote for if you wish.

@travisbell Thanks so much Travis.