Why we've built Apiwatch

Modern tech companies use existing APIs instead of building complex features themselves. They use the Stripe API to handle payments, for example, or the Mailchimp Marketing API for e-mail and the Facebook Graph API to enrich customer profiles.

But when you use all these APIs, how do you keep track of what APIs are used where? Let alone: what the entire API landscape of your organization looks like?

An API provider ourselves, we noticed that many developers struggle to manage their API integrations. When we sent out major API changes – like the deprecation of a version or a change in our subscription plan - our support inbox overflowed. We got messages that the registered contact person had left the company; another company had no idea which one of their many projects was using the API; credentials got lost; developers had missed updates, or they discovered that they hadn’t been using the API anymore (but were still paying for it).

We were amazed with how much trouble companies were having with the APIs they use. So, we decided to do something about it and built Apiwatch to let you regain control of your API integrations.

Jasper van Elferen

Jasper van Elferen

Dimitri van Hees

Dimitri van Hees