References
In-depth explanations of the concepts, parameters and values you'll encounter across the MusiMap platform.
What you'll find here
The References section is the dictionary of cross-cutting platform concepts. error shapes, pagination, OAuth scopes, and the machine-readable OpenAPI contract. If you need how to call an endpoint, start with the Web API guides instead.
Catalogue model
Reference for the music information MusiMap can represent in your workspace catalogues: artists, works, tracks, releases, and related structures.
Catalogue model overview
Entity types, identifiers, classifications, and the Queen example.
Artists
Names, life events, credits, and classifications.
Tracks
Recordings, duration, explicit status, ISRCs, and credits.
Integration
Conceptual guides for decision-makers: where MusiMap fits, how data gets in, and how intelligence returns to your platform without replacing your existing workflow.
How MusiMap integrates
Product models, catalogue sources, and where MusiMap fits in your platform.
Getting data into MusiMap
S3, SFTP, managed storage, supported inputs, and ingestion timing.
Getting results back
Immediate response, API retrieval, webhooks, files, and push delivery.
V1 reference pages
OpenAPI spec
Interactive browse of every V1 endpoint plus raw JSON download.
Errors
OAuth and /v1/* error envelopes, error_code registry, debugging tips.
Pagination
Shared list envelope. count, page, page_size, has_next, results.
Scopes
OAuth scopes declared for each implemented V1 endpoint.
Atlas
Read-only MusiMap Atlas. scopes, search include flags, and inventory paths.
Related
Ready to integrate?
Start with the quickstart guide or browse the OpenAPI spec for every V1 endpoint.