Right now, Akita generates OpenAPI 3 specs on a subset of all supported content types.
Our roadmap includes gRPC and GraphQL, so please get in touch if you're interested and we'll let you know when that's ready.
Akita currently supports the most popular API content types and we are working to add new content types. We welcome requests!
Supported Content-Types include:
Character Set Support
By default, Akita supports the UTF-8 and ASCII character sets. If your API is using a different character set (example: latin-1) you will need to specify it using the
charsetattribute in the
You can determine if your API is compatible with
apidump by running the following cURL command against one of your API endpoints. This command will make a request to your API and return just the headers we need to determine compatibility.
curl -s -o /dev/null -D - https://app.akita.software
After successfully running the command above you should see output that looks something like the example below. To determine if your API is supported by Akita ensure the value in the
Content-Type header is listed in the Supported Content Types table above. In this example, the
Content-Type value is
application/json which is supported by Akita.
HTTP/1.1 200 Date: Tue, 14 Jul 2020 23:21:19 GMT Content-Type: application/json; charset=utf-8
If you can't use
apidump, don't worry! You can still generate HAR files from your browser or proxy tool.
Updated 4 months ago