Base URL
Authentication
All requests require a bearer token obtained through the magic link flow. Pass the token in theAuthorization header:
Resources
| Resource | Description |
|---|---|
| Skills | Org-scoped tasks that captures are recorded against |
| Captures | Recorded spatial sessions |
| Objects | 3D models used in captures and courses |
| Organizations | Tenant accounts and member management |
| Users | User identity and member profiles |
Endpoint reference
The full endpoint-by-endpoint reference and interactive playground are currently internal-only — they aren’t published here yet. Holos engineers can preview them locally; see the holos-docs README. The OpenAPI 3.1 spec is generated from and maintained in theholos-api repository.
The pages below cover the concepts you need to integrate: authentication, webhooks, error shapes, and the per-resource guides.
Concepts
Authentication
Session tokens and the bearer flow
Webhooks
Event notifications via Stytch and Svix
Errors
Error format and status codes
