If specified as a number with no units, will be interpreted as a percent. Service sabnzbd.resume Service data attribute The SABnzbd API key of the service instance (unique per SABnzbd integration). Service sabnzbd.pause Service data attribute
#SABNZBD API KEY DOWNLOAD#
This component will create these sensors: attaching rename script: Key From Newznabprovider"&priority=-100&cat=comics&script=ComicRN.pyĬompleted send-to-SAB link: Key From Newznabprovider"&priority=-100&cat=comics&script=ComicRN.If the above My button doesn’t work, you can also perform the following stepsįrom the configuration menu, select Devices & Services.įrom the list, search and select SABnzbd.įollow the instructions on screen to complete the setup. attaching category: Key From Newznabprovider"&priority=-100&cat=comics setting priority: Key From Newznabprovider"&priority=-100 attaching nzb provider link: Key From Newznabprovider" Link to retrieve via api: "API Key From Newznabprovider" In below log I replaced my Newznab Provider API and my SAB API, and what I am seeing is that the &apikey if used twice in the final url which is send to sab. Maybe this helps in finding the exact issue? Sab is using the FIRST apikey and gives the error about wrong api instead of using the SECOND apikey at the end of the url. I tried to find out what is happening and I have the feeling that the apikey entry in the url is being mis-interpreted. Unless I'm completely missing something (as a novice, I'm happy to admit that), maybe that's where it's going wrong? Oddly enough, it looks like the "api?t=get&id=" value being passed is not the same as what NZBGeek uses, which is my API key. I swapped out my actual API with that "rUHu6QhKkNALMyMwUwTLpxH7pQGjzMBM" value again:ġ 18:20:11 - INFO :: Thread-14 : Found The Walking Dead (2014) issue:ġ 18:20:11 - INFO :: Thread-14 : Successfully sent nzb file to SABnzbdġ 18:20:11 - INFO :: Thread-14 : setting the nzbid for this download grabbed by NZBGeek (newznab) in the nzblog to : api?t=get&id=49112f94f0a65f5837f6ĭ1301e1f1eb0&apikey=rUHu6QhKkNALMyMwUwTLpxH7pQGjzMBMġ 18:20:11 - INFO :: Thread-14 : passing to updater.ġ 18:20:11 - INFO :: Thread-14 : Updating status to snatchedġ 18:20:11 - INFO :: Thread-14 : Updated the status (Snatched) complete for The Walking Dead Issue: 134 what Mylar currently does).įor the record, this is what I'm seeing in Mylar (sorry I forgot to include this earlier). However, I'm still running into the same "API Key incorrect" problem between Mylar and SAB, which makes me think you may be onto something with the way they handle their calls (vs.
#SABNZBD API KEY FULL#
For the record, NZBGeek uses the NZB key in SAB, rather than the full API key. I've since corrected this gaff and everything is working fine on that front. I did some checking on my end and found that the program I use for DNS somehow started using my private IP, rather than public, which would explain the problems I was having sending the NZBs to SAB from the NZBGeek website. Get ?t=get&id=rUHu6QhKkNALMyMwUwTLpxH7pQGjzMBMĭownloads the nzb file associated with an Id. Include &extended=1 to return extended information in the search results. Returns a list of nzbs matching a book based query. You can also filter by site category or group name by including a comma separated list as follows ?t=search&cat=1000,2000&group=a.b.multimedia. Use the parameter ?t= to specify the function being called. Your credentials should be provided as ?apikey=rUHu6QhKkNALMyMwUwTLpxH7pQGjzMBM I replaced my actual key with a 32-digit string, for the sake of privacy/etc, but both the "?apikey=" and "Get ?t=get&id=" entries had the same value (my NZBGeek API key): No problem, reopening for the sake of investigation.
0 kommentar(er)
