App data
Custom fields a connected app keeps on anything in Aden (tracks, albums, events, playlists, teams, users, organisations, ...), for what Aden has no field for yet. Namespaced per app, same access rules on the MCP and the API.
What it is
When an app you connect to Aden (ChatGPT, your own website, a tool built on the Aden API) needs to remember something Aden has no field for, it can keep it as app data on anything in Aden: a track, an album, an event, a playlist, a contact, a team, an organisation, or you. A mood, an external id, a sync status, a note for your label's own system.
Each app only sees what it saved itself. Disconnect an app and its data stays attached to that app, never to another one.
Using it
- In ChatGPT: ask "save the mood 'late night' on Donuts". ChatGPT confirms, then keeps it. Ask for it back any time.
- From your own app:
GET,PUTandDELETEon/api/v1/app-datawithentityType,entityId,key(andvalueto save). A read-only key or a read-only connection can read but not save.
Limits: 64 KB of JSON per value, 100 keys per app on one thing.
Let Aden pitch a track
A track's Pitched list and Up next offer "Let Aden pitch this". Allowing it files an ordinary pitch to Aden's own organisation, with the deal kinds and a rights confirmation. Up next then follows what Aden does with it.
Custom board columns and sub-boards
Add a tag or genre column between the statuses, or a sub-board under a status or another column. Dropping a track (or album) in one sets its status, tags and genres; each column chooses whether leaving it takes the value off. Shown on the tracks board, list, sidebar, status dropdown, desktop and mobile, and on the albums board and list.