API References
All authenticated endpoints accept a JWT in the Authorization: Bearer <token> header — either a session JWT or an API token.
| Service | Base URL |
|---|---|
| Auth | https://auth.cloud.eddisonso.com |
| Compute | https://compute.cloud.eddisonso.com |
| Storage | https://storage.cloud.eddisonso.com |
| Notifications | https://notifications.cloud.eddisonso.com |
Service Pages
- Auth API — Login, sessions, and API token management
- Compute API — Containers, SSH keys, ingress, and terminal access
- Storage API — Namespaces, file upload/download, and public access
- Notifications — Real-time notifications, mute preferences, and WebSocket push
Token Scopes
API tokens support resource-specific scopes with up to 4 segments:
<service>.<user_id> # all resources in service
<service>.<user_id>.<resource> # all items of resource type
<service>.<user_id>.<resource>.<id> # specific item only
Compute examples:
compute.<uid>.containers— access all containerscompute.<uid>.containers.<container_id>— access one specific containercompute.<uid>.keys— access all SSH keys
Storage examples:
storage.<uid>.namespaces— manage all namespacesstorage.<uid>.namespaces.<name>— manage a specific namespacestorage.<uid>.files— access files in all namespacesstorage.<uid>.files.<name>— access files in a specific namespace
Broad scopes cascade: a token with compute.<uid>.containers grants access to all individual containers. A token with compute.<uid>.containers.<id> only grants access to that one container.
Errors
All errors return JSON:
{ "error": "description of what went wrong" }
| Status | Meaning |
|---|---|
400 | Invalid request |
401 | Missing or invalid authentication |
403 | Insufficient permissions |
404 | Resource not found |
409 | Conflict |
500 | Internal server error |