Now we're going to show you how to navigate the map of your API.
Head over to the Akita console to see what we learned. It can take up to 10 minutes to build your first model. If you don't see it, hang tight!
Here you'll see a time series chart showing the aggregate traffic that went into the model, as well as a list of APIs observed. Each API shows its P99 latency and the number of requests observed, as well as the structure and types of its requests and responses.
You can drill down into each endpoint to learn more about it.
Each endpoint shows the path and query parameters, headers, and body fields expected in a valid request, as well as the kinds of responses the endpoint supports.
Fields are labeled with their types (
int, etc.) and, when possible, specific data formats, like
phone number, and so on. You can find a complete list of data formats in Supported Data Formats .
Akita represents API models as annotated YAML files that you can download and use anywhere OpenAPI3 specs are used. What you see in this model is also what Akita uses for semantic diffing across API models.
If you want to clean up what you see, you have a few options:
Updated about 1 month ago