Feature Requests:
Intervals API - sooner or later?

1. •  
     CommentAuthorMichael
   • CommentTimeApr 24th 2007

    
   We are trying to gauge how much an API with Intervals would help our current customers. An API is on every Web 2.0 checklist, but we have focused our attention on listening to our customers and rolling out features that are most in demand.
   
   We have the core in place for an API in our framework are wondering if we should execute it sooner rather than later. Much to our surprise, many of our customers have been asking for more and more features and have not been clamoring for an API. They have been looking to use Intervals as their one stop place for all task, time, and project management needs.
   
   As web developers ourselves, we expected more API demand so here is your chance to sound off. Would you use an API? Should we move it to our list of features to execute sooner rather than later?
   
   As always, thanks for you thoughts - Michael
2. • CommentAuthorrobertgay77
   • CommentTimeJun 29th 2007

    
   Our firm is definitely interested in an API as we would like the ability to exchange information captured in Intervals easily with other systems that are not web-based. Also, we are interested in any ability to link from other websites into Intervals.
   
   Robert
3. • CommentAuthormlandis
   • CommentTimeAug 6th 2007

    
   We would have interest in an API. We would like to import time into Dynamics GP as invoices and that would be great.
   Thanks,
   Matt
4. • CommentAuthordnlomnimedia
   • CommentTimeJan 24th 2008

    
   A full API would definitely be of interest to my company. We would love the ability to exchange Intervals data with other online and offline applications.
5. • CommentAuthorjnhearne
   • CommentTimeFeb 7th 2008

    
   An API would be nice, but I think There are still some features that could be added before much attention is given to an API. For Instance, figuring out a way to get Pay (hourly, daily, weekly) listed on a resources info. This would help to determine margins. Let's figure this out before diving into an API
6. •  
     CommentAuthorjreeve
   • CommentTimeMar 14th 2008

    
   API Update
   We have begun development of the Intervals API and hope to launch soon. To give you a sneak peak inside of the API development, here is what you can expect:
   

   
   
   1. Authentication will use HTTP Basic Authentication
   
   
   2. The API will be accessible using POST requests
   
   
   3. Your Intervals data will be available via the API in both XML and JSON formats.
   
   
   4. Request lists of data or individual items
   
   

   
   
   Next Steps
   We still need to API-enable the individual actions (task lists, project lists, etc) and start testing. Meanwhile, we're finalizing the API documentation. We are considering launching a read-only API for now, to get it launched sooner, and then follow-up with a fully functional read-write API. So now is a good time to let us know your thoughts on the API. Do you have any ideas for us? Any needs for us to consider? Let us know.
   
   API Sneak Peak
   Here is an example, from our pending documentation, of how API calls will work:
   
   Request
   
curl -H 'Accept: application/xml' -u jreevius:wh4t1tb3l1k3 http://url

   
   Response
   
<?xml version="1.0" encoding="utf-8"?>
<item>
<key>value</key>
<key>value</key>
</item>

7. •  
     CommentAuthorjreeve
   • CommentTimeApr 23rd 2008 edited

    
   The API is in its early stages of development. We are writing documentation and layering API aware code throughout the application. If you'd like to try it out, here is a way to use the API to start and stop timers:
   
   To start a timer:
   curl -k -H 'Accept: application/xml' -u [username]:[password] http://[yourdomain]/timer/start/0/[taskID]/
   
   To stop a timer:
   curl -k -H 'Accept: application/xml' -u [username]:[password] http://[yourdomain]/timer/stop/0/[taskID]/
   
   To clear a timer:
   curl -k -H 'Accept: application/xml' -u [username]:[password] http://[yourdomain]/timer/clear/0/[taskID]/
   
   For example, here is how I would start, stop, and clear a timer for task #14754:
   curl -k -H 'Accept: application/xml' -u jreeve:wh4t1tb3l1k3 http://pelago.projectaccount.com/timer/start/0/14754/
   curl -k -H 'Accept: application/xml' -u jreeve:wh4t1tb3l1k3 http://pelago.projectaccount.com/timer/stop/0/14754/
   curl -k -H 'Accept: application/xml' -u jreeve:wh4t1tb3l1k3 http://pelago.projectaccount.com/timer/clear/0/14754/
   
   Next up...
   Now that the basic foundation of the API has been built, we'll be API-enabling different areas of Intervals. The first areas to be retrofitted will be task views and lists.
   
   Give the timer API calls a try and let us know what you think!
8. • CommentAuthormlandis
   • CommentTimeApr 30th 2008

    
   Could you give a quick example of using your API using vbscript, vba or visual basic?
   Just to point me in the right direction...
   
   Thanks,
   Matt