[Request]Expanded User Stats in API

[MysteryGodzilla]

Would love to have expanded stats in the user api like seedsize, uploads, average seedtime. I have a dashboard for my trackers to show progress for the next user group, some fields I need to manually update as they arent available in the api. This could also be useful for implementation into apps like Qui to check indexer details.

[Roardom]

It's a good idea, and there's a PR implementing it here: #5181.

Before expanding the API further, I'd like to see apikeys with separate permissions (search, download, upload, user) that way when an apikey from one software gets leaked (happens waayyyy too often), it doesn't affect all endpoints. I've been working on such a feature locally, but still need to finish it (or if someone else beats me to it, that'd be great as well).

I should mention though that UNIT3D is not the only tracker software out there and I would highly recommend that qui does not integrate directly with UNIT3D, but instead for there to be an intermediary like jackett that connects the two. That way if/when the api gets changed, only the jackett equivalent would have to be updated, and not qui.

[MysteryGodzilla]

Thanks for the response. Totally agree, I would also feel more comfortable inputting a stats only api key into third-party software, or into my own dashboards. Great call with extra security.

Also agree, I mentioned qui as I would like to see the data arrive through to my instance, but of course with many different trackers an implementation into prowlarr, jacket or a future replacement indeed seems like the best location to pull inital api stats data.

For now I'll keep using what I can for my custom tracker dashboard and either manual enter some fields or userscript scrap website profile data