hoox from hooxi

Inspiration

Webhooks play a very important role in the integration lifecycle for an enterprise. Sometimes, they are the only mechanism to get real time data from within a SaaS solution. However, the configuration mechanism for Webhooks across the SaaS landscape is extremely fragmented - Some solutions offer an API mechanism/some via a UI console and some provide both. It is a pain for Developers to have to go through these multiple mechanisms to figure out how to configure Webhooks.

hooxi's mission as a company is to make webhooks adoption easy for both Developers and SaaS companies and that is why we have developed "hoox from hooxi".

What it does

This Postman Collection (called "hoox") aims to make life easy for developers by providing a centralized API registry which helps developers discover/manage and test the configuration of Webhooks offered by a SaaS solution via a REST API. This collection is classified by area in which the SaaS solution operates and contains all the possible operations to help configure and maintain webhooks. No more time spent in pouring through the entire internet for figuring out webhook configuration. hoox from hooxi helps you get started immediately.

And in case a SaaS solution does not provide an API, this collection will help understand the importance of a Webhook API enabling wider adoption.

How we built it

Postman Collections/Environments

Challenges we ran into

Non-standardization of the API's across different SaaS solutions.

What's next for hoox

hoox from hooxi will continue in the long run and aim to be the centralized API repository for any kind of configuration of Webhooks offered by a SaaS provider. The workspace could be expanded to include all kinds of SaaS providers which offer a Webhook configuration via a REST API. Collaborators will be able to create their own hoox via a fork and this can be merged back into the main workspace.