IntroductionGet your Record API keyQuickstartAuthenticationCatalogue lifecycleDestinationsRecord AIWorkspace and rolesOverviewSend worksShare semanticsCatalogue routingValidation and gapsLoad a full catalogueEndpoint referenceOverviewSingle lookupBatch lookupRoadmapErrorsRate limits and retriesGlossaryVersioning

Partner Metadata API

Roadmap

Endpoints designed for this surface but not yet live.

The namespace grows per data point as use cases firm up, so you request exactly what an asset is missing:

  • GET/api/v1/metadata/assets?isrc=|iswc= : resolve statement identifiers to Record asset IDs.
  • GET/api/v1/metadata/assets/{id}/identifiers : ISWC, all known ISRCs, external IDs.
  • GET/api/v1/metadata/assets/{id}/contributors : name, CWR role code, IPI, PRO, provenance.
  • GET/api/v1/metadata/assets/{id}/ownership : writer ownership and publisher collection shares (two distinct values, never merged).
  • Holder-scoped GET/holders + GET/catalog with an updated_since delta cursor for bulk sync.
  • An outbound "doorbell" (we POST a sync request; you pull) for on-demand pushes from our side.

A contributor payload will key a person on a stable Record id plus every IPI they hold. One person often holds several. An IPI alone is not a unique key for a person.