- August 09, 2016

It has been some time since we released the very first public available version 0.3. The version already included all the main components: history, repository, and contexts. That was on September 15th 2011. The DHC team will soon be celebrating its five year anniversary. introduced HATEOAS support in form of hyperlinks

Our ultimate goal has always been to make API testing and discovery as simple as possible, to help you improve your productivity by keeping you focused on what to do instead of how to do it.

We started with just a simple HTTP client which has evolved into a tool allowing you to do manual and automated, complex API testing.


DHC 0.7.19 brought assertions, a way how to validate a response


And finally, the latest version supports complex API scenarios, automated testing with Maven plugin, while also providing a support for team collaboration


I like using the the expression: evolved. The reason is that not a single feature has been removed. If we add something new, we always keep all existing functionality. It’s just on you to discover new features and start using them. Checkout DHC evolution in time on G+ stream.

I’m also proud to say that another cool stuff is coming soon, following the same principles and policy. Here is a screenshot of what’s coming, just to give you a little sneakpeek:

Pasted image at 2016_07_26 11_51 AM

Yes, you see right, DHC will give you BDD aligned testing soon! Be ready to be surprised 😉


Over the years we have been developing DHC, the Chrome Store team has introduced a new packaging concept and has set a deadline. The packaging that DHC is currently using will ultimately get deprecated. This literally means that all the applications using the old packaging will be removed from the Chrome Store. That should be in late 2016.

Source: Chromium Blog

We have two options to keep DHC available on the Chrome Store after the current DHC packaging deprecates. We can migrate DHC to a packaged app or to an extension.

Although we like the concept of packaged apps giving you a standalone app experience, it takes its price. E.g. XMLHttpRequest (XHR), which is a crucial component used by most of web applications, and even by DHC, to send and receive HTTP requests and responses, is not available. Moreover, a packaged app content security policy is too strong that even opening an external link is forbidden. Because of that, a migration to an extension seems to be the only option allowing us to keep the current user experience, allowing us to keep all existing functionality without breaking anything.

We want to be ready and keep DHC available on the market, so don’t be surprised when DHC gets updated to an extension. Also, there is at least one positive outcome. You will get a DHC icon next to the URL box. You will be able to open DHC in just one click, directly from a Chrome browser and without the need to switch to the Apps page!


Thank you dear users, for all the support we have received during the years and for using DHC!