Page 1 of 1

Missing "Path" property in API Call "queue"

Posted: October 4th, 2013, 1:02 pm
by cyberkyro
Hi folks,

I developed my own (Windows) app to accomplish a preview feature for queued job's.
Unfortunately I have issues to get always the correct temporary path for a queued job item (uncompleted downloads) using the API - Especially if the queued job was renamed or the download was started twice.

I know it's easy to get the base directory for the temporary folder through the API, but not the full path for a single queued job.
For completed jobs there exists a property called "Path" (history\slots\slot). which is exactly what I need for queued items (queue\slots\slot)

Best regards,
cyberkyro

Re: API: Missing "Path" property for queued job items

Posted: November 3rd, 2013, 9:38 am
by shypike
Sorry for the late reaction, it was on my to-do for a long time.
However, I think the field that you're looking for is already present in the API call "history".
It's called ""storage" : "/path/to/Videos/Series/Title/Season 3/Title.S03E04.Episode"

Re: API: Missing "Path" property for queued job items

Posted: November 15th, 2013, 6:41 am
by cyberkyro
Hi,

Thanks for your response.

Unfortunately that's not the variable what i'm looking for...
a) The API call "history" contains only completed or failed Downloads, but not Downloads they are still in progress (Status=Downloading, Paused, Queued...)!
b) The "Storage" property from the API call "history" contains the {extraction path}, not the {temporary/incoming path}!

The {incoming/temporary path} is already available in the "path" property which only exists in the API call "history", but not in the API call "queue".

Hopefully, the "path" property will be available in the API call "Queue" in later versions of sabnzbd ;-)

I need this variable (incoming/temporary path, not the extraction path) for Downloads they are still in Progress!

Best regards,
Cyberkyro

Re: Missing "Path" property in API Call "queue"

Posted: November 15th, 2013, 3:11 pm
by shypike
Clear, I'll see what I can do.
But it is a minority request obviously or do you see a wider audience for your tool?