Get a Spotify track · Spotify API
Returns a Spotify track by id: title, duration, play count, explicit flag, album and artists. Returns `not_found` when the track does not exist.
Using ChatGPT, Claude Code or another client? See the setup steps
curl https://api.unifapi.com/spotify/tracks/{id} \
-H "Authorization: Bearer $UNIFAPI_KEY"Parameters
- idpathrequired
- Spotify track id, as in open.spotify.com/track/{id}.
- The parameter for this Spotify operation. Use the URL-visible slug or id described in the docs.
This operation is part of the Spotify API in the music category. It uses the same Bearer token, request tracing, error model, and billing envelope as every UnifAPI endpoint, so agents can switch between platforms without custom per-vendor glue code.
Use it when a workflow needs Spotify public data alongside other music catalogs, but should still keep one API key, one account balance, and one predictable JSON contract.
Common agent workflows
- Look up public Spotify data for agents that need reliable open-web context.
- Give an AI agent a stable Spotify data source without building a per-platform integration.
- Normalize Spotify responses into the same UnifAPI envelope used across the catalog.
Unified envelope, platform-native fields
- Lookup responses return one canonical object in `data` with stable identifiers, source URLs where available, and platform-specific metadata normalized into predictable JSON.
- The operation has a 3 credits ($0.003) minimum charge, so `billing.records_charged` can be higher than the visible records returned.
- A not-found or invalid-input condition uses the unified UnifAPI error shape, so callers do not need special handling for each source platform.
Response status codes
Billing
This operation charges 1 credit per billable record, with a 3 credits ($0.003) operation minimum. Public responses include billing metadata with credits charged, records charged, and remaining workspace balance. Incorrect Credit deductions caused by platform failures can be restored as billing corrections.
Errors and retries
Authentication, validation, rate-limit, not-found, and provider errors use the unified UnifAPI error format. Agents should log `request_id`, retry only retryable failures, and treat invalid API keys, disabled keys, and expired keys as the same public `unauthorized` error type.
Fields in the data object
A successful Get a Spotify track call returns one data object with these fields (12 of 13 shown — the docs list the full schema).
- platformstring | null
- Platform for this track. One of: spotify.
- track_idstring | null
- Stable Spotify track identifier.
- titlestring | null
- Track title.
- duration_msnumber | null
- Track duration in milliseconds.
- track_numbernumber | null
- Track number on the album when available.
- is_explicitboolean | null
- Whether the track is marked explicit when available.
- is_playableboolean | null
- Whether the track is playable in the current context.
- play_countnumber | null
- Play count when available.
- media_typestring | null
- Media type when available.
- preview_urlstring | null
- Short audio preview URL when available.
- track_urlstring | null
- Canonical public Spotify track URL.
- albumobject | null
- Album details when available.
More Spotify operations
Combine endpoints from the same platform, then join the results with other UnifAPI categories without changing authentication or response parsing.
Get a Spotify album
Returns a Spotify album by id: title, artists, release date, label, cover art and tracks. Returns `not_found` when the album does not exist.
Get a Spotify artist
Returns a Spotify artist by id: name, genres, followers, monthly listeners, world rank, related artists and discography. Returns `not_found` when the artist does not exist.