Loading API documentation…
A complete guide to authenticating and building across the Astravera ecosystem.
The Astravera suite operates on a multi-service architecture where distinct backend APIs focus on specific domains while sharing a unified database state and Reverb real-time transport mechanism.
Astravera utilizes Laravel Sanctum for SPA authentication and stateful sessions, and Laravel Passport for cross-service internal OAuth token validation.
To interact with Kairos or Nomia, the user must first authenticate with Hermes.
GET http://localhost:8081/sanctum/csrf-cookiePOST http://localhost:8081/login with email and passwordhermes_session). Cross-domain requests must include withCredentials: true.Every user belongs to one or more Workspaces. Most Kairos and Nomia endpoints automatically resolve to the active CurrentWorkspace defined on the User model. Use Hermes to manage the user's active workspace state before making execution requests against Kairos. Use the Accept: application/json header to ensure correctly formatted API validation errors.
All backend activity across Hermes, Kairos, and Nomia is broadcasted synchronously via the centralized Astravera-Reverb WebSocket server. When connecting to the public WebSocket port (default: 6001), use the shared astravera-key to subscribe to user-specific private channels for real-time item creation and signature progress updates.
Select an API from the top navigation to view interactive endpoint documentation.