AutoWeb Inoreader

Since we already have an API for Feedly it would be nice to have one for Inoreader as well.
The API seems to be documented well and offers a bunch of different methods.

 

Thank you very much for such a quick implementation!
I did a short test and everything seems to work as expected.

Please don't understand my posts in this subforum as support requests, I'm just sharing some ideas I can't realize by myself.


Currently, I use Inoreaders IFTTT integration to mark all articles of certain subscriptions as read, when older than x days.
Unfortunately, IFTTTs choice is quite limited (1; 2; 3; 7 or 14 days), so I was hoping to be able to mark articles as read older then 6 or 36 hours through AW.

As I understand Inoreaders API documentation it allows to specify this timespan in seconds, right?
Do you think it's possible to implement this method as well?

 

It seems to work, but Tasker throws the following error:

Code (Text):

13.42.37/E FIRE PLUGIN: AutoWeb Web Service / com.twofortyfouram.locale.intent.action.FIRE_SETTING: 13 bundle keys
13.42.37/E AutoWeb Web Service: plugin comp: com.joaomgcd.autoweb/com.joaomgcd.autoweb.broadcastreceiver.BroadcastReceiverFire
13.42.37/E add wait type Plugin3 time 120
13.42.37/E add wait type Plugin3 done

 

Error Message:
a.a.b: A JSONArray text must start with '[' at 1 [character 2 line 1]

 

What was the solution, please? I have a similar error using several apis, I didn't manage to get only one to work. I am sure, the mistake is mine, but what is it?

 

To be precise: I tested Google Cal and Yes/No several times and got the error each time. I now tested Spotify and it worked. I will have a look into it, but if someone has a hint ...

 

Got it for yesno: The api was buggy, it must be https instead of http. This one now works for me, I now shared my version in hope everybody can get the working version.

 

There is none, I still wake up every morning with a ton of error notifications.
Could you find out, whats causing them, @joaomgcd?

I'm not sure these are related to the issues you have with other APIs, @Optimisc