There is currently a big problem with the discover functionality that the fields with_watch_providers & with_watch_monetization_types do not combine. So if for a example i run a search for something with Apple TV as the watch provider and 'flatrate' as the monetisation type... EXPECTATION: i get stuff currently streaming on Apple TV REALITY: I get the combination of everything on Apple TV (regardless of monetisation type), and everything available on a 'flatrate' (regardless of provider).

I understand there are no current plans to fix this issue and so i am trying to think of ways to achieve the use-case outlined in the expectation.

My initial thought was to simply search based on watch providers only, and then filter out any results that don't have a 'flatrate' monetization submap. However this is NOT possible because the data structures returned by the discover endpoint does not include any information on watch providers... So what i would need to do is get my list of 20 results with my discover call... then re-query each of those results on the [mediatype]/[id]/watch/providers endpoint which would obviously be very demanding on the API.

Looking at it from the other angle... I'm wondering if it would be possible for you to simply include a 'watch_providers' list in the data structures output by the discover endpoints? Just a simply list of the id's would be fine.

This way, i could discover everything available in my region with the 'flatrate' monetization type... Then, knowing nothing in the resulting list needs to be paid for, cycle through each result and extract the ones where the watch_providers list contains an id of a service owned by the user... The chances of getting multiple results on each page would be pretty high so there would be little need for further queries with this approach meaning much less strain on the API.

Can you please confirm if this is something you can put into action, and if so how long you think it might take?