Has `type` with an explicit value become mandatory or is there some other issue with the API?

Hello,

A query that has always returned results via the web API, suddenly no longer does.

This is the request (headers are sent but omitted here) that returns zero results:

/api/v1/subtitles?episode_number=1&languages=en&query=friends&season_number=1

If I add the no_guessit query param to an otherwise identical request, then 230+ results do show up:

/api/v1/subtitles?episode_number=1&languages=en&no_guessit=1&query=friends&season_number=1

On the other hand, adding the type query param (we have always relied on the default of all) but not no_guessit, also returns 230+ results:

/api/v1/subtitles?episode_number=1&languages=en&query=friends&season_number=1&type=episode

Has type with an explicit value become mandatory or is there some other issue with the API?

Any help is appreciated.

I worked on the case, now if you send an episode or season number you won’t need a type - the API will figure out you are not searching for a movie

the search was also vastly improved when it comes to searching on the titles, please try again your exemples with “friends”, things should work better now

1 Like