I’m pretty sure anything that can be done in the webUI can be done via the API but I have not found anywhere in the documentation on how to blacklist a release with the API. I think I’ll use a browser extension to watch the requests to find it but does anyone know if this is documented? Also, I am trying to use this to blacklist certain release groups from certain qualities in a custom script (so restriction tags aren’t sufficient). But say I have a custom scripts that executes on grab, sees the release is not from the desired release group and sends an API call to blacklist the release. Will that release still get processed and sent to the client since it was blacklisted mid-process?
Not documented currently. Chrome dev tools (specifically the networking tab) should show you every it’s doing.
The download has already been sent to the download client by the time the On Grab custom script is run.
Ok, so undocumented but possible. What will happen then if my script blacklists the release on grab? If it’s already been sent to the client, will it immediately be stopped or will it continue to download? I’m just wondering if it will behave differently this way.
If the queue has been updated already you could remove it from queue and blacklist it, which would do both. If you marked it as failed it would not remove it from the queue.
Ok, thanks. I’ll try to update the wiki on the API command as well, once I find the time.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.