Disappointed: My *arrs sit behind a reverse-proxy. I don't require an API key to access them

[serendrewpity]

Disappointed: My *arrs sit behind a reverse-proxy. I don't require an API key to access them. So, I can simply navigate to hxxp://www.example.com/*arr and get to radarr, sonarr, and lidarr. But I can't use your extension because it requires me to enter the API key. Which I can supply, but I'd rather not.

[trossr32]

You don't need to provide an API key for the extension to work. The only reason the extension uses an API key at the moment is to identify the version of *arr that you're using so that it can set the correct Search Path URL and Search Field Selector in the settings in the Advanced settings tab.

These settings should default to the correct values for the latest versions of *arr, so as long as your *arr instances are up-to-date you should be good to go.

Obviously you'll still need to set the Protocol, domain and port so that the extension can redirect to your *arr instances from integration sites like IMDb.

Here's where the *arr API is called, as you can see it's just getting version info: https://github.com/trossr32/sonarr-radarr-lidarr-autosearch-browser-extension/blob/master/src/content/js/core.js#L747