I first met the founders when we were all working together at the same company. Their professional chemistry and passion for user, nay, developer experience is palpable. API Changelog filled a hole in the developer process and I know Hitch will fill in the rest, enabling companies of all sizes to build successful API communities.
@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.
Excited for the relaunch of API Changelog as a stand-alone business! I've known @bpedro since his Tarpipe days (an earlier attempt at something like Zapier meets Yahoo! Pipes). They've taken everything they've learned and poured it into a suite of tools for managing APIs and community.
@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.
@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
@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!
@acpmasquerade Thanks for the feedback, Dhruba! Can you be more specific about the error you're seeing. You can contact me directly on bpedro@hitchhq.com. Thank you so much!
@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'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.
Have been using programmeable web for years now and have also been getting weekly updates on apis i follow, what makes this different or special from programable web
@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.
You can't beat the combo of @bpedro and @LukeAM for knowing the API community and what it needs. Hitch sounds like the answer to a lot of the industry needs - I'm excited to give it a spin.
API changes : a real problem. For the API supply chain. For integration. For trust.
Looking forward to see Hitch become the API credit rating agency.
#HitchIsTheNewFitch
@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!
Remotes.in