Spotify Track API
Resolve a public Spotify track by id or share URL and get title, duration, album context, and credited artists in the shared Social Fetch envelope.
GET /v1/spotify/track1 credit per successful request.
About this endpoint
Music-aware creator tools often start with a track link pasted from Slack, a CRM note, or a TikTok sound attribution — not a full album crawl. You need the stable Spotify track id, title, duration, and which artists are credited so you can join that row to a person or campaign record.
`GET /v1/spotify/track` accepts either `trackId` or a public `url` (`https://open.spotify.com/track/…`). One of those params is required. On a found lookup you get `data.track` (id, title, durationMs, trackUrl, playable, optional playCount / previewUrl / explicit), plus `data.album` and `data.artists` when present. Branch on `data.lookupStatus` before you write rows — HTTP 200 alone does not mean the track resolved.
Pricing is on the credit badge for this operation; bill from `meta.creditsCharged`. This route is single-track detail. Artist cards and album 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 Track API FAQ
How do I get Spotify track metadata via API?
Call GET /v1/spotify/track with your Social Fetch API key (x-api-key) and either a trackId or a public open.spotify.com/track/… url query param. Read data.lookupStatus, then data.track, data.album, and data.artists. Full parameters are in the API docs.
How much does the Spotify Track 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 track response include?
When found: data.track (trackId, title, durationMs, trackUrl, playable, plus optional fields like trackNumber, explicit, playCount, previewUrl), data.album when available, and data.artists (artistId, displayName, optional avatar and profile URLs). Always branch on data.lookupStatus first.
Can I pass a Spotify track URL instead of an id?
Yes. Pass url as a public https://open.spotify.com/track/{id} link, or pass trackId directly. One of trackId or url is required per request.
Does a completed lookup always mean the track was found?
No. HTTP 200 means the request finished. Check data.lookupStatus: found means you got track details; not_found means the id or URL did not resolve. Persist meta.requestId when you need to debug a miss.
Spotify track vs album or artist endpoints?
This route fetches one track. Use the Spotify album and artist routes on the same hub when you need full album or artist cards. 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.