Hitch - Where developers stay informed of API changes & discussion

@chrismessina @bpedro This is great. Always wondered why API docs are not made keeping technical people in mind. A lot of non-tech people wanna use APIs to serve business needs but fail to do so because of the jargon involved.

@chrismessina Thanks, Chris! I really appreciate all the input you've been giving us since the Tarpipe days :-).

@sarthakgh Thanks for your kind words, Sar! That's exactly why we're launching Hitch: to bring APIs to the greater, non-technical audience. Please keep sending any feedback. /cc @chrismessina

@chrismessina @bpedro ditto! Couldn't have said it better myself. Genius team at work.

@andr3 Thanks a lot, André! Please let us know if you have any comments or suggestions. /cc @chrismessina

@medjawii That's a great comparison, Mehdi! Being able to fulfill that would make us all very proud. Thanks for your valuable input.

@bpedro I know some modest minds who tried to solve it too. http://www.programmableweb.com/n... You have all my support!

@bpedro you should also check with @adamd with its new initiatives as everydeveloper.com and http://www.docstocode.com/

@medjawii I know ;) That makes your comment even more valuable. Thanks!

@bpedro The business model at the end of such "agency" was to sell SaaS/API insurance, coupled with API Terms of service Changelog support/advises and SLA guarantee. Go for Hitch now!

@jordiromero Thanks for sharing your thoughts, Jordi! We believe the community features really help API owners better understand their audience.

@rotemthegolfer Thanks, Rotem!

@jkriggins Thank you so much, Jen! A lot of what we're doing is a result of the many conversations we've been having with you around APIs. Please keep sharing your ideas and feedback.

@basictechy That's a great question, Andrew! Thanks for reaching out. The main difference is that we actually track any changes on API documentation (HTML and also machine-readable) and will notify you whenever there's a change. Other differences include our ability to use Swagger, RAML and WSDL and automatically render a nice looking API Reference. I invite you to take a look at Slack's API on Hitch and see these different features in action: https://www.hitchhq.com/slack Thanks again and please don't hesitate to share any feedback.

@svetlyak40wt Thanks for asking, that's a great question! It's fully automated. We periodically read API machine-readable documentation and compare it with a previous version generating a changelog and notifying all the API followers. What happens if an API doesn't have machine-readable documentation? We help them migrate to machine-readable and, in the meanwhile, we parse and generate differences from their HTML documentation.

@bpedro I think, you need to build an enterprise self hosted version. It will be valuable in big companies with large amount of internal APIs.

@svetlyak40wt That's a great suggestion! Do you have any particular company in mind that would benefit from this product? Thanks!

@bpedro I'm working at Yandex. We have a lot of APIs and libraries. Not sure how many of them are parsable by Hitch though. But for now I'm planning to deploy an internal version of my own pet-project, it is about changelogs too but not tied to APIs.

@lindybrandon @lukeam Thanks for the kind words, Lorinda! Please let us know if you have any comments or suggestions.

@anant_garg Hi Anant. Thanks for the feedback. We're addressing that issue right now and will update here shortly.

@anant_garg Hi again, Anant. The issue has now been fixed. Please let me know if you're still having difficulties signing up. Thank you so much for your great feedback!

@bpedro Sure! Just thought I'd let you know. Also your API list has some dummy entries at the bottom.

@anant_garg Thanks again! We're not yet filtering the API list but we'll do it soon. BTW, is there any kind of filter you'd like to see there?

@bpedro @anant_garg oauth.io? ;)

@malcolmbell Thanks, Malcolm!