Good day, eh.  There’s been a small update to the API that some of you might already have noticed.  We added an <auth_url /> element, in the style our existing <url /> tag, for invoices, estimates and clients.

The new <auth_url /> requires an authorized session to work, and is intended to provide an administrative link to your target object.  Since we didn’t have a client <url /> element in the client.get response, we’ve included that for consistency.

<auth_url /> will honour an existing administrative session, if you have already logged into the application in some way. It will NOT auto-magically direct you to a secure administrative page without prompting you for user and password if you haven’t already logged in.  So don’t get’em mixed.  <url /> is for client links, <auth_url /> is for you.

Summary:

• client.get:
  • <url /> added to response
  • <auth_url /> added to response
• estimate.get:
  • <auth_url /> added to response
• invoice.get:
  • <auth_url /> added to response

Our API documentation has been updated to include this element where necessary.

Allo Freshies!  My name is Mike (no, not McDerment), and I’ll be one of your API developers.  I say “one of your API developers” as we have a whole team now (there are two of us).  So be prepared for updates big and small.

Since I’m the second Mike in the office, I’ve been barraged with nicknames since I joined up.  Because my last name is Gauthier, there are a few variations I will respond to.  Mikey G or MG would work.  G-man?  Michael?  Embarrassing.  But since Mike McDerment doesn’t really post on the Developers blog, I can hope and dream of being just ‘Mike’ again.  We can keep that between us.

From here on in, we intend to post more frequently than we have.  Our last blog post was in June, and that’s just not cool.  Also, please feel free to get in touch with us via the developer forum.  My teammate Dan (introduction forthcoming) and I will be actively monitoring our community and addressing developments and concerns both here and there.