Developers
Build on top of Aden with the typed SDK and the public REST API.
Everything the Aden web and mobile apps do runs on the same public API at
https://www.aden.space/api/v1. You get the same surface, plus an official
TypeScript SDK with types inferred straight from the server.
SDK Quickstart
Install @adenspace/sdk and make your first typed request.
Authentication
API keys for integrations, Supabase sessions for user-facing apps.
API Reference
Every endpoint, grouped by resource, from the live OpenAPI spec.
Concepts
How tracks, albums and teams are modeled behind the endpoints.
What you can build
- Release automation: push albums, tracks, and versions from your DAW or release tooling.
- Collaborator workflows: invite contacts, assign splits, and manage sessions from your own UI.
- Dashboards: pull streaming stats, milestones, and calendar events into internal tools.
- Bots and sync: post into team threads from CI, or mirror tracks into Notion, Linear, or Airtable.
How it's shaped
| Piece | What it is |
|---|---|
| Transport | Plain REST over HTTP + JSON, versioned under /api/v1 |
| Spec | OpenAPI 3.0, live at /api/v1/openapi/json |
| Types | Eden Treaty. Inferred from the server, no code generation |
| Auth | Team API keys (aden_live_…) or Supabase session tokens |
Using Aden rather than building on it? Start in the Help center.
Was this helpful?