I have seen that T411 was asked as indexer, but you won’t add it for the reasons you explained (no API, web scrapping not a solution to develop for you).
But i’m sure that many users out there (and i’m one of them) already wrote such a script (in python in my case) to find all my missing french episodes on T411.
For every missing episode, i give my script a few parameters (title show, tvdbid, imdbid, season, episode, …) and it will find and download the corresponding torrents.
So if you create a generic indexer that we should activate by indicating a script to execute (you decide the parameters you will send, but they should be like the ones i use so i can find the right stuff), we could have a solution where you don’t have to scrape.
For the returning result of the script, it’s on you to decide : we can copy the resulting torrents at some place, or give the result via a new endpoint in the api.
With such a generic indexer, all the users who want to use a tracker that you won’t add, will have a solution.
We’ll be adding a generic RSS feed. Which could support searching via a standard interface, but it wouldn’t be script based, it would need to emulate the RSS feed.
In the mean time for the searching you could use Sonarr’s API and get the missing episodes, then search for them, all from your script.
@Taloth what do you think about the searching aspect of a generic RSS feed?
I already did this, but not with the api : seemed easier to me to directly read in the db sqlite.
Concerning your proposition with RSS, I had the idee of a better integration in sonarr.
With your solution, i don’t think i could use the icons to download manually/automatically a specific episode.(from T411).
With my generic indexer, that should work.
It would need to work the same way the search works for any other indexer, it would just proxy it, the same way your script works, but it would be available as a web interface.