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.
I think that your redevelopment of API documentation would be an interesting series of blog articles in and of themselves. Giving examples of bad documentation decisions, giving examples of how they were corrected in the new documentation, etc. There are lots of examples of refactoring code, but entirely too few that deal with refactoring the manual.
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.