26 March 2006 ~ 5 Comments

Basecamp API released

After a slight delay, the long awaited Basecamp API is now available. The documentation is a little on the light side, but rather straightforward. They give some examples using curl and some Ruby code to get you started. Remember that you have to explicitly enable the API for your account before it will work.

I tried some of the examples. You basically get XML responses that look something like this:



  Thinkhole Labs
  
  


  United States
  235827


  true
  http://thinkhole.org
  thinkhole


  Eastern Time (US & Canada)
  

So the question is, who will be the first person to make a nice Python module that handles the API in its entirety? I would imagine it won’t be long before you’ll be able to put ‘import basecamp’ at the top of your script.

I think having an open API will get a lot more people to look at their product. A very good move on their part if you ask me. Of course, 37Signals does reserve the right to “modify or discontinue, temporarily or permanently, your access to the API (or any part thereof) with or without notice.”

Ah… the joy of not owning your own applications!

Update: Here’s the announcement on the SvN blog and the API forum.

5 Responses to “Basecamp API released”

  1. jpc 26 March 2006 at 5:24 pm Permalink

    I think you’ve got some accidental spaces in the middle of XML tags containing ‘-’. ;]

  2. John 26 March 2006 at 6:26 pm Permalink

    Good call.

    I’m currently using the Preserve Code Formatting plugin, and it looks like it is adding the spaces when I save the post. I can remove the spaces, but WP puts them right back in. I just tried Geshi and Code Markup, but they introduce other problems themselves.

    Grrrr :)

  3. John 27 March 2006 at 12:50 am Permalink

    jpc: I tweaked my stylesheet and I think the spacing issues are fixed. Although… there might still be something a little wonky with IE6.

  4. jpc 28 March 2006 at 12:42 am Permalink

    It looks good in Safari… Who cares about IE6? ;]


Leave a Reply