3 ms·
The irony of this statement "At Ticketmatic, we promise that anything you can do through the user interface is also available via the API." in the context of
by jasonlotito 12y ago
The irony of this statement
"At Ticketmatic, we promise that anything you can do through the user interface is also available via the API."
in the context of the article is amusing. Going to the website, I find no mention of an API anywhere. I can only guess that it's API documentation hidden behind a login. This is the worst kind of API documentation. I've dealt with APIs like this far too often to find it friendly. In every case, it's been frustration.
Regardless, while the platitude is agreeable, this is literally an article that says nothing more than what fit into a tweet.
- baconomatic 12y agoHad to do a little searching, but here it is: https://app.ticketmatic.com/api/doc https://app.ticketmatic.com/api/doc
- rubenv 12y ago(Author here) 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.
- Sanddancer 12y agoI 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.