The Next-generation API Observability Platform

How do you know if a small code change can take down your site? What's really going on with your APIs? At Akita, we're building tools to help you answer that question.

Akita watches calls to web APIs in order to help you visualize your service graph, monitor your APIs, make sense of your request/response logs, and 💥 catch breaking changes 💥.

By passively watching traffic, Akita integrates in a low-friction, low-risk way, making it possible to run in CI/CD, staging, or production without too much overhead. Akita's API modeling technology to automatically catch breaking changes.

Get Started    FAQs

What is Akita?

Akita watches calls to web APIs in order to help you:

  • Visualize your service graph
  • Monitor your APIs
  • Make sense of your request/response logs
  • 💥 Catch breaking changes 💥

How Akita works

Akita passively watches network traffic via pcap filters and/or framework integrations in order to:

  1. be blackbox,
  2. run in CI/CD, staging, or production, and
  3. use API modeling technology to automatically catch regressions.

Our client only sends back request and response metadata to the Akita cloud, meaning Akita never sees potentially sensitive data in your requests and responses.

Getting Started with Akita

  1. Follow this tutorial to use Akita with the Akibox demo service.
  2. Follow this Quick Start to use Akita to model AJAX APIs from the browser. This technique also works if you are using a standard proxy tool, for instead the Charles Proxy.
  3. Follow this Quick Start to use the Akita agent to model traffic going to one of your services. Note that you can also generate traffic to a service by using Postman Collections.
  4. Learn about how to Integrate with Integration Tests.
  5. Learn about how to use a Proxy for Encrypted Traffic.

Updated about a month ago



What is Akita?


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.