Processed Information

Processed information is the data generated from raw sales and streaming reports after ingestion, normalization, parsing, and aggregation.

Sales reports received from distributors and digital service providers contain raw consumption data — such as streams, downloads, territories, revenue shares, and usage events — often delivered in different structures and formats. OAS processes this information and organizes it into meaningful reporting entities, allowing users to analyze performance and royalties at multiple levels.

After processing, data is grouped according to core music industry entities, including tracks, artists, and releases, following standard industry association relationships.

At this stage, processed information has not yet been fully validated against the catalog, meaning some inconsistencies may still exist, such as duplicated artists, alternate track naming, unmatched releases, or metadata variations originating from source reports.

Catalog validation is handled separately by the catalog module, which standardizes and reconciles these entities to improve accuracy for downstream royalty calculations and reporting.

Core Processed Entities

• Artist An artist represents an individual performer, group, or credited recording artist associated with one or more releases and tracks. Because collaborations are common, a release or track may have multiple artists.

• Track A track represents an individual sound recording or musical work reported in sales or streaming data. A track may appear on one or multiple releases and may be associated with one or multiple artists.

• Release A release represents a commercial music product — such as an album, EP, or single — containing one or more tracks. A release may be associated with multiple artists.

Why this organization matters

Organizing raw report data into these entities allows OAS to transform distributor reports into structured royalty data, making earnings analysis, royalty management, and performance reporting easier to understand and consume through the API.

This structure also supports royalty calculations at different levels, such as per track, per release, per artist, by territory, or by distributor.

Artists

GET /api/artists/

This route allows to get a list of artists per active organization

Example

curl -X GET "https://oas-beta.ottomate.me/api/artists" \
    -H "Authorization: Bearer YOUR_TOKEN"

Request body

Note

No form data required

Response

200 OK — Successful

Field	Type	Description
id	integer	Artist ID
created	date	Creation Date
modified	date	Modification Date
name	string	Artist Name
total_local	Decimal	Total revenues attributed to artist
aliases	list	List of possible aliases linked to artist.
is_percentege _modified	boolean	Indicates if the revenue percentage has been modified
organisation	integer	Organization ID which artist is linked.

401 Unauthorized — Invalid credentials

{"detail": "Authentication credentials were not provided or are invalid."}

Tracks

GET /api/tracks/

This route allows to get a list of tracks per active organization

Example

curl -X GET "https://oas-beta.ottomate.me/api/tracks" \
    -H "Authorization: Bearer YOUR_TOKEN"

Request body

Note

No form data required

Response

200 OK — Successful

Field	Type	Description
id	integer	Artist ID
created	date	Creation Date
modified	date	Modification Date
title	string	Track Title
display_artist	string	Main Artist Name
number	integer	Official track number
volume	integer	Official track volume
isrc	string	Unique 12-character alphanumeric code
total_local	Decimal	Total revenues attributed to artist
organisation	integer	Organization ID which artist is linked.

401 Unauthorized — Invalid credentials

{"detail": "Authentication credentials were not provided or are invalid."}

Releases

GET /api/releases/

This route allows to get a list of releases per active organization

Example

curl -X GET "https://oas-beta.ottomate.me/api/releases" \
    -H "Authorization: Bearer YOUR_TOKEN"

Request body

Note

No form data required

Response

200 OK — Successful

Field	Type	Description
id	integer	Artist ID
created	date	Creation Date
modified	date	Modification Date
title	string	Release Title
display_artist	string	Main Artist Name
release_id	string	Unique 12-character numeric code
total_local	Decimal	Total revenues attributed to artist
organisation	integer	Organization ID which artist is linked.

401 Unauthorized — Invalid credentials

{"detail": "Authentication credentials were not provided or are invalid."}