API Changelog & Hitch

As many of our early users know, before we became Hitch, we started as API Changelog. This service was built to help API developers (primarily consumers) stay informed when APIs changed via a single channel.

Developers loved this as they were automatically informed each time documentation changed for an API they used. API Changelog would identify and scope changes, and notify developers whenever they occurred. Less time and effort researching for developers and more time actually building product.

As we have broadened our scope at Hitch, we’ve also improved the original API Changelog functionality:

• Better scoping and identification of when change occurs (less false positives)
• Clearer access and layout of changes, so you can better discover what is taking place.
• Size of change definitions, meaning we inform you of the estimated impact of the change.
• Better notifications: email, json, xml and in the Hitch app.

So with Hitch you can continue saving time and effort of staying up to date and follow APIs for free. However we’ve taken it a step forward: now anyone can list their API and get a free changelog for their service.

Just add an API, submit your documentation, and we will do the rest. It is still 100% free for any public API.

Private API Changelog

Additionally, if your API is 100% private, we can also help. Last week we launched Teams and Private APIs, allowing you to get a changelog which is only available to a controlled group of people.

Hitch for Teams is a very cost effective way to keep control over access to your API documentation and developer community.

Just go to Hitch, create a team and control who gets informed and when. It’s that easy.

—

If you like this article, please click on the ❤️ button below and follow this publication so you don’t miss out.

Ready to start engaging and growing your API community with Hitch? Sign up now.