Audit log
Every organization has an audit log, at Team & controls → Audit log (/organizations/<id>/audit). Only Owners can read it. It records:
| Area | Records |
|---|---|
| Members | Organization created, membership granted or revoked, with the member and the role |
| Sign-in and provisioning | Domains added and verified, SCIM tokens issued and revoked, people provisioned and deprovisioned, service account keys created and revoked |
| Launch controls | Launch limits and budget alerts changed |
| Launches | Every event of the launches filed under the organization (requested, live-checked, confirmed, created, labelled, stopped, terminated), with the permanent offering, provider, GPU and region ids |
The audit log reads the organization's existing append-only histories. Nothing in it can be edited or deleted. A window spans at most 366 days and holds at most 10,000 records; truncated: true means more exist after the last record returned.
Export a window as CSV or JSON Lines from the page, or read it with a service account key.
Service accounts
A service account is an API key that belongs to the organization instead of a person. Use one for a FinOps pipeline, a SIEM or a dashboard. Owners create them at Team & controls → Service accounts.
- The key is
kvo_followed by 48 hex digits. It is shown once, and Kovara keeps only its SHA-256 hash. - Service account keys can only read. The permissions are:
costs:read: the organization's launch cost report and FOCUS exportlaunches:read: the launches filed under the organizationaudit:read: the audit log
- A service account can never request, confirm or stop a launch.
- A key expires after 30 days to 2 years, or never. It stops working when it expires, when it is revoked, or when the Owner who created it is no longer an active Owner. Removing a person therefore also retires the keys they made.
- An organization can have at most 20 active keys. Creating and revoking keys is recorded in the audit log.
- Personal developer keys (
kvk_) do not work on these endpoints, and service account keys do not work on personal ones.
API
Every request sends Authorization: Bearer kvo_….
| Endpoint | Permission | Returns |
|---|---|---|
GET /api/v1/org/whoami | any | The organization, the key's name, its permissions and its expiry |
GET /api/v1/org/audit-log?since=&until=&format=json|jsonl|csv | audit:read | The audit log, oldest first. The default window is the last 24 hours. ISO 8601 times. Header X-Kovara-Truncated |
GET /api/v1/org/costs?from=&to=&format=json|csv|focus | costs:read | The cost report of the organization's launches (details) |
GET /api/v1/org/launches | launches:read | The latest 200 launches filed under the organization, with their instances |
Errors: 401 for a missing, invalid, revoked or expired key; 403 when the key lacks the permission; 422 for invalid parameters; 413 when there are too many cost lines; 503 when the service is unavailable. Launch costs and launches answer 404 while launches are switched off on the platform.
Example: forward the last hour of audit records to a SIEM every hour.
since=$(date -u -d '-1 hour' +%Y-%m-%dT%H:%M:%SZ)
curl -sf -H "Authorization: Bearer $KOVARA_SERVICE_KEY" \
"https://www.kovaragrid.com/api/v1/org/audit-log?since=$since&format=jsonl" >> kovara-audit.jsonl