Nope, that's the old one for V2 (which isn't very good).

We're currently releasing the third generation of the Ticketmatic platform, where one of the big efforts is in improving the developer story.

That's not public yet, for which I apologise. There will be a beautiful developer program soon.

I didn't think that the article should wait on that. It's the idea that matters and didn't want any discussion to turn into a nitpicking over what we did right (and wrong).

This article mostly came out of a frustration with bad API documentation and I was hoping to inspire people to do (slightly) better.