What do you like best about the product?

Zuplo have made it so easy for us to build a customer-facing API with minimal engineering time, and their support has been very responsive. Zuplo handles the API docs, API key management, integrates with our auth, syncs with git, etc. It handles all our needs and lets us focus on building our product.

What do you dislike about the product?

I've been missing a few minor features in their automatic docs, but this is all changing soon with their move to Zudoku - which brings lots of flexibility to the API docs.

What problems is the product solving and how is that benefiting you?

We're using Zuplo both for a public API that we expose to our customers, and for an internal API that sits between our front-end web app and AI models in our backend. For the public API we use the API key management service, and we use a bunch of policies to handle everything from rate-limiting, auth to metering. There's even a caching policy which is brilliant for some of our frontend needs. We also use Zuplo's developer API for webhooks coming from our auth provider so that we can set additional metadata on each API consumer. All working great.