Use case

Verify releases after music delivery

Locate platform listings, reconcile catalog data, and track release propagation across music services.

Delivery and catalog verification are different jobs. After a distributor sends a release to music services, product and operations teams still need to find the public listings, reconcile their metadata, and show where the release is discoverable. Musicfetch turns a release URL, recording ISRC, or release UPC into normalized catalog data and matched service entries for that post-delivery workflow.

Where Musicfetch fits after delivery

Start with the strongest identifier your release pipeline already has, then ask Musicfetch to search the destination services relevant to your dashboard or operations queue.

Starting point and lookup	Distribution-platform job
Known release listing → Album URL lookup `GET /url`	Resolve one confirmed listing and locate the same release on other services
Recording ISRC → ISRC lookup `GET /isrc`	Locate a delivered track and reconcile its platform entries
Release UPC → UPC lookup `GET /upc`	Locate an album or release and collect its service IDs and public links

Current ISRC and UPC lookups use Spotify as their initial catalog source. A valid identifier that is not available there may not resolve, so use a known release URL when one is available and keep an unresolved state in your workflow.

Four post-delivery workflows

Locate public listings. Resolve a release URL, ISRC, or UPC and search selected services for matching tracks or albums after delivery.
Check propagation. Compare the service keys actually returned with the destinations your release workflow expects, optionally within a country.
Reconcile catalog data. Store normalized names, artists, artwork, dates, identifiers, and each matched service's platform ID and link.
Update your dashboard. Show discovered listings, queue follow-up checks for missing matches, and attach public links to release records.

Measure discovery without overstating delivery status

A returned service key means Musicfetch found a catalog match for that lookup. An omitted key means no match was returned at that time; it does not prove that delivery failed, that a release is unavailable in every territory, or that the DSP rejected it. Treat catalog matching as an observable propagation signal alongside your own delivery receipts and platform reporting.

Generate promotional links from verified listings

Once matches appear, use the returned links to populate campaign tools, artist dashboards, or downstream promotional workflows. If you also operate a public cross-platform landing page, see the separate fanlink and smart-link builder guide for UI and fallback considerations.

Check a release by UPC

The live example starts with a release UPC and requests all 40 service keys currently exposed by Musicfetch. The other tabs show the same workflow from a known release URL or track ISRC. These are server-side requests; keep the access token private.

curl "https://api.musicfetch.io/upc?upc=00602537618132&services=amazon,amazonMusic,anghami,appleMusic,audiomack,audius,awa,bandcamp,beatport,boomplay,deezer,discogs,flo,gaana,genius,iHeartRadio,instagram,jioSaavn,joox,kkbox,lineMusic,musicBrainz,napster,netease,pandora,qobuz,qqMusic,sevenDigital,shazam,soundcloud,spotify,telmoreMusik,tidal,tiktok,trebel,yandex,youtube,youtubeMusic,youtubeShorts,youseeMusik&country=US" \
  -H "x-token: YOUR_TOKEN"

Live UPC lookup response

This is a real Musicfetch response refreshed on the server. The JSON contains the service keys actually matched by the lookup; requested keys that did not match are not inserted as placeholders.

Live data

{
"result": {
"type": "album",
"name": "So Long, See You Tomorrow",
"image": { 3 items },
"description": "The story of London’s Bombay Bicycle Club is one of constant evolution: since their 2009 debut, the band have woven together elements of everything from wistful indie folk to crystalline math rock. The outfit’s fourth album is a warm, rewarding coalition of these pursuits, offering emotional, synth-driven rock complemented by richly textured samples, big synths, and the dizzying melodies of frontman Jack Steadman. A sampled Bollywood loop introduces the opener, “Overdone,” while the sweeping, R&B-inspired groove of “Home by Now” is anchored by cello and splices of digitally manipulated piano. The hypnotic percussion and eight-bit groove of “Feel” result in the album’s finest track, while “Whenever, Wherever” opens as a pensive ballad before adopting a driving dance beat. A fuzzy kalimba sample and polyrhythmic drumbeat close So Long, See You Tomorrow, finishing an entrancing ride.",
"releaseDate": "2014-02-03T00:00:00.000Z",
"label": "Universal-Island Records Ltd.",
"copyright": "©℗ 2014 Universal Island Records, a division of Universal Music Operations Limited",
"distributor": "Universal Music Group",
"totalTracks": 10,
"upc": "00602537618132",
"genres": [ 1 item ],
"services": {
"amazonMusic": { 2 items },
"anghami": { 2 items },
"appleMusic": { 2 items },
"audiomack": { 2 items },
"awa": { 2 items },
"bandcamp": { 2 items },
"beatport": { 2 items },
"deezer": { 2 items },
"discogs": { 3 items },
"flo": { 2 items },
"genius": { 2 items },
"joox": { 2 items },
"kkbox": { 2 items },
"lineMusic": { 2 items },
"netease": { 2 items },
"pandora": { 2 items },
"qobuz": { 2 items },
"qqMusic": { 2 items },
"sevenDigital": { 2 items },
"shazam": { 2 items },
"soundcloud": { 2 items },
"spotify": { 2 items },
"telmoreMusik": { 2 items },
"tidal": { 2 items },
"trebel": { 2 items },
"yandex": { 2 items },
"youseeMusik": { 2 items },
"youtube": { 2 items },
"youtubeMusic": { 2 items }
},
"artists": [ 1 item ],
"tracks": [ 10 items ]
},
"messages": [ 1 item ]
}

Map the response into a release dashboard

Response field	Suggested use
`result.name`, `artists`, `image`, `releaseDate`	Populate a normalized release summary
`result.isrc` or `result.upc`	Reconcile the match with internal delivery identifiers
`result.services.{service}.id`	Store the service-specific catalog identifier
`result.services.{service}.link`	Link operators, artists, or campaign tools to the public listing
Presence or absence of a requested service key	Record a discovery signal for this lookup time and country

Production checklist

Keep the release URL, ISRC, and UPC attached to the same internal release record so your workflow can use the strongest available lookup.
Request an explicit destination set and pass country when localized links matter.
Store the lookup time and country with returned service IDs and links.
Model a missing match as pending or unresolved—not automatically as a failed delivery—and apply your own retry schedule.
Keep the Musicfetch token on your server, cache useful results, and handle lookup errors independently for each release.

Add catalog verification to your release workflow

Start with a 7-day free trial, then use the API documentation to connect your first lookup.

Start 7-day free trial

Building the promotional destination too? Read the fanlink and smart-link builder guide.