Concepts
Concepts
How tracks, albums and teams are modeled, and how to drive them from the API.
These pages explain Aden's core resources in detail: the data model, the lifecycle, and the endpoints that drive them. Use them when you're building an integration that goes beyond a single endpoint and want to understand how the pieces fit together.
Tracks
Versions, covers, collaborators, comments, todos, and the release lifecycle.
Albums
Group tracks into releases, manage collaborators, and ship a record.
Team
Members, invites, plans, socials, and the shared workspace model.
How to read these pages
Every feature page follows the same shape:
- What it is: the concept and where it shows up in the product.
- Data model: the resource, its key fields, and how it relates to others.
- Lifecycle: the states a resource moves through and what triggers them.
- Endpoints: the relevant API surface, grouped by intent.
- Recipes: short, copy-paste SDK snippets for the common jobs.
For the full request/response schema of any endpoint, jump to the API Reference.
Was this helpful?