REST API Reference
The full, current endpoint reference for KubeOpera API — applications, deployment history and rollback, CloudSpaces and vClusters, CI/CD pipelines, and Kaniko builds — lives on that service's own page rather than being duplicated here. Keeping one copy avoids the reference silently drifting out of sync with itself as endpoints are added or changed, which is exactly what happened to this page previously.
As covered in the API Overview, none of these routes are meant to be called directly by an external client — they're the frontend's own internal proxy targets, authenticated by a logged-in user's session. For programmatic or agent-facing access to the platform, see the MCP Server instead.
Response conventions
A few conventions hold across every route on this service, worth knowing before reading the endpoint tables:
List endpoints return either a flat JSON array or a small envelope object (commonly {"data": [...], "total": N} for paginated resources) — check the specific endpoint's description for which shape applies. Errors follow the platform-wide convention documented in the Security Guide's error-handling notes: a 4xx response carries a JSON body with a human-readable message field, never a raw upstream error or stack trace.
Next Steps
- KubeOpera API service page — the actual endpoint reference
- MCP Server Tools — the equivalent surface, exposed as agent-callable tools