Hi @monkeydodev,

Please give us a full example request so we can see what might be happening.

Hi Travis,

I would love to an believe me i tried... But whenever i try and send a message on this forum with a pasted query i get receive an error dropdown stating simply 'Error There was a problem' and i can't send the message... I don't know if it's some particular character it has an issue with... there's just no way of knowing...

Hopefully you can reconstruct with the following details

Endpoint: discover/movie

language: en-US
vote_average.gte=8
vote_count.gte=100
with_genres=18|1075
sort_by=vote_count.desc
watch_region=GB
with_watch_providers=8|9|2|337|103
with_watch_monetization_types=ads|free

ok that seems to have worked with my typing in manually... If you try with the above settings you should receive zero results.. but if you change monetization types to either ads or free you should get results

Hi Travis,

Upon further experimentation i believe the 'with_watch_monetization_types' field might be ignored entirely if you enter a single value...

The behaviour seems to be...

• if you enter multiple pipe separate values you get no results,
• if you enter a single value it's as if you entered null,

The reason i say this is that when using the discover/tv endpoint to find comedies in the GB region, specifying 2 as the only watch provider (apple TV) and 'flatrate' as a monetisation type... It gives me 'The Rookie' in the results...

When you look up the watch providers for 'The Rookie' from the /tv/79744/watch/providers endpoint you can see there are infact only 2 'flatrate' watch providers for the GB region (10 & 49)... Sky Go and Now TV respectively... However, 'Apple TV' is listed as a watch provider under the 'buy' monetisation type so it seems the monetisation type filtering just isn't working.

Pasting in the AXIOS formatted request from your API reference page below... hopefully this will work

import axios from 'axios';

const options = {
  method: 'GET',
  url: 'https://api.themoviedb.org/3/discover/tv',
  params: {
    include_adult: 'false',
    include_null_first_air_dates: 'false',
    language: 'en-US',
    page: '1',
    sort_by: 'popularity.desc',
    'vote_average.gte': '8',
    'vote_count.gte': '100',
    watch_region: 'GB',
    with_genres: '35',
    with_watch_monetization_types: 'flatrate',
    with_watch_providers: '2'
  },
  headers: {
    accept: 'application/json',
    Authorization: 'Bearer eyJhbGciOiJIUzI1NiJ9.eyJhdWQiOiJiNmUxNTgxNjJkM2M4ZWEzNmZiZmI5ZDI3ZTU1MWUyMCIsInN1YiI6IjYyZjRmNjcwNTk0Yzk0MDA3YWE2ODgxMiIsInNjb3BlcyI6WyJhcGlfcmVhZCJdLCJ2ZXJzaW9uIjoxfQ.mrQ777N-OCo6kAs_liisF2oShyWtCDHKEd0yoGt5S90'
  }
};

axios
  .request(options)
  .then(function (response) {
    console.log(response.data);
  })
  .catch(function (error) {
    console.error(error);
  });

Hi @travisbell

Sorry to blather on about this one but are you able to provide a rough ETA on how soon you reckon you'll be able to look into this one?

I know you've got a dozen other things on your plate but my release is pending on this feature working properly. If you think it's going to take a while to get to this one, no worries, just let me know and i'll defer this feature to a future release.

Kind regards Alex

Hi @travisbell

Turns out that passing multiple values DOES work... The problem was on my end... The issue was that i was including spaces around my pipe separation... so 'free | flatrate' rather than 'free|flatrate'... The spacing is not an issue in fields that accept multiple number inputs, but it does turn out to be a problem for fields with multiple string inputs. This may have been obvious to a more experienced developer than myself. Apologies.

Happy to hear you sorted this out.