Resolves one UPC to a release, its recordings and known platform track matches. Supply upcs as a single string value; repeated parameters and extra comma-separated values return HTTP 400 before lookup work. Approved API keys can have a higher input limit, up to 10, while response and work bounds remain shared across the request. Catalog data comes from Apple Music with Deezer fallback; only exact normalized UPC matches are accepted. Saved Spotify occurrences are joined through the existing ISRC index; no UPC index or Tracks collection scan by UPC is used. This endpoint does not ingest Spotify counterparts for every album recording. Up to 100 recording rows total, 100 distinct ISRC joins, five saved Spotify occurrences per recording, and 600 combined native/saved platform entries are returned per request. Saved matches are ordered by valid popularity descending, unknown popularity last, then Spotify ID. Bounds are applied before track hydration; native catalog paging is capped at 100 tracks per UPC. Native platform identities take capacity before optional saved matches; if native identities alone exhaust the bound, additional recordings are omitted rather than returned without a catalog identity. An incomplete catalog, missing ISRC, unavailable join or reached bound sets partial=true; use the paginated ISRC lookup for more stored Spotify occurrences. This is a bounded preview of known matches, not a worldwide or territorial coverage guarantee. Client waiting budget: 10 seconds. Complete positive catalog results are cached in process until eviction/restart, clean misses for five minutes, and incomplete results for 30 seconds. No discover, force, update or caller-controlled account-limit parameter is supported. Existing provider pacing and fail-fast protection are reused without adding an API queue.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||