Spotify Album API
Resolve a public Spotify album by id or share URL and get release metadata plus an ordered tracklist in the shared Social Fetch envelope.
GET /v1/spotify/album1 credit per successful request.
About this endpoint
Release calendars and music CRM rows usually start from an album link, not a single track paste. You need the stable album id, title, label, release date, cover art, and the tracklist in order so you can join that release to a campaign or creator record.
`GET /v1/spotify/album` accepts either `albumId` or a public `url` (`https://open.spotify.com/album/…`). One of those params is required. On a found lookup you get `data.album` with identity fields (albumId, title, albumType, albumUrl, playable), optional label / releaseDate / coverArtUrl / copyright, credited artists, `trackCount`, and `tracks` in track order. Branch on `data.lookupStatus` before you write rows — HTTP 200 alone does not mean the album resolved.
Pricing is on the credit badge for this operation; bill from `meta.creditsCharged`. This route is single-album detail. Artist cards and individual track lookups are separate Spotify paths under the same tag and API key. Playback, user libraries, and playlist management stay on Spotify's official Web API with OAuth.
Spotify Album API FAQ
How do I get Spotify album metadata via API?
Call GET /v1/spotify/album with your Social Fetch API key (x-api-key) and either an albumId or a public open.spotify.com/album/… url query param. Read data.lookupStatus, then data.album. Full parameters are in the API docs.
How much does the Spotify Album API cost?
Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged — that field is the billing source of truth.
What does the Spotify album response include?
When found: data.album with albumId, title, albumType, albumUrl, playable, trackCount, and tracks (ordered). Optional fields include label, releaseDate, coverArtUrl, copyright, and artists. Always branch on data.lookupStatus first.
Can I pass a Spotify album URL instead of an id?
Yes. Pass url as a public https://open.spotify.com/album/{id} link, or pass albumId directly. One of albumId or url is required per request.
Does a completed lookup always mean the album was found?
No. HTTP 200 means the request finished. Check data.lookupStatus: found means you got album details; not_found means the id or URL did not resolve. Persist meta.requestId when you need to debug a miss.
Spotify album vs track or artist endpoints?
This route fetches one album, including its tracklist. Use GET /v1/spotify/track for a single track and GET /v1/spotify/artist for an artist card. Same API key across the Spotify tag.
Does this replace the Spotify Web API?
No. Social Fetch returns public catalog metadata for enrichment pipelines. Use Spotify's official Web API when you need playback control, user libraries, or OAuth-scoped playlist access.