It’s been a while since my last update here. Apologize.
We completely understand that API is a great feature to have, it is #1 idea in UserVoice and lots of you guys are still waiting for it. Shame on us.
But so far we are not ready for it. It’s a huge chunk of work to implement, document and maintain. We believe that at the moment we have more important work to do, as all forces now are allocated to release of a new version of our product.
We would like to release and nail it down, only after that we would consider other changes.
I’ll try to keep you guys posted.
MikeJacek Tomaszewski commented
So much time has passed and still no API ;o
Too huge chunk of work to implement? API can be self-documented, and doesn't need additional time to be maintained, if you keep it versioned.
For me now I'll have either to do it myself by scraping your website or choosing a different timetracking tool. Sadly I think I'll have to go with the other option ;/Jacek Tomaszewski commented
Just a comment of me as an experienced full stack developer: this should be your priority right now! If you want to improve features like browser extensions or make mobile applications possible, then you should create a simple API authable via user's auth token.
If you'd do that, then CSV reports wouldn't be that needed, as I would be able to create it from JSON myself easily.
P.S. I'd love to create a simple Android & iOS "Everhour" app using Ionic Framework during some night hackaton, maybe even with an extension for Android Wear smartwatches , but API is a must for me to do that ;]
In the following article we are sharing some scenarios that (hopefully) explain the complexity we are referring to and how we’re going to address it in the new version.