Back to All

Why is Akita not extracting path variables?


When viewing your spec, you might notice endpoints like GET /users/foo, where you know that foo is really a path variable.

Akita can generally infer path variables if given enough examples of the API calls. If an API endpoint is missing path variables, make sure Akita is able to observe at least 2 successful calls to the endpoint using different values for the variable.

For example, if Akita observes:

GET /users/foo
GET /users/bar

then Akita can correctly infer the path variable and generalize the path as GET /users/<arg2>.