Akua publishes an OpenAPI 3.1 specification that describes every endpoint, parameter, and response shape in this documentation. Use it to generate type-safe clients in any language, validate requests in your tests, and keep your integrations in lockstep with the API.Documentation Index
Fetch the complete documentation index at: https://docs.akua.dev/llms.txt
Use this file to discover all available pages before exploring further.
Where to get the spec
The spec is available in two forms:| Source | URL | Use case |
|---|---|---|
| Live API | https://api.akua.dev/v1/openapi.json | Always reflects the deployed API. Cache this for production codegen pipelines. |
| Static snapshot | docs/openapi-public.json | Versioned alongside the docs. Use for CI builds that need a stable input. |
docs/openapi-public.json or the build fails.
Generate a client
Most languages have mature OpenAPI codegen tooling. Pick whichever fits your stack:TypeScript and JavaScript
openapi-typescript generates a single .d.ts file with no runtime dependencies. Pair it with openapi-fetch for a type-safe fetch wrapper.
Go
The Akua CLI usesoapi-codegen to generate a strongly-typed Go client.
Python
openapi-python-client emits a Pydantic-typed package.
Other languages
The OpenAPI Generator project ships generators for 50+ languages, including Java, C#, Rust, PHP, and Ruby. The Akua spec is plain OpenAPI 3.1 with no vendor extensions, so any compliant generator works.Versioning
The API path includes a version segment (/v1/...). Breaking changes ship under a new version path; the previous version stays available for at least 12 months after a new one launches.
Inside a version, Akua follows additive evolution:
- New endpoints and new optional fields can appear at any time.
- Existing fields are never removed or renamed within a version.
- Validation rules can tighten (rare; flagged in the changelog).
Stay in sync
For CI pipelines that consume the spec, pin to the static snapshot file in this repository and bump it deliberately:Related topics
Introduction
API base URL, conventions, and error envelope.
Authentication
Workspace API tokens and JWT auth.
CLI reference
The Akua CLI built on top of the same API.