Spotify reference
Spotify API guide
Discover music, resolve the correct entity type and collect a bounded playlist or podcast sample. Artist, album, track, playlist and show identifiers are not interchangeable.
Quickstart
Start with Spotify
Discover music, resolve the correct entity type and collect a bounded playlist or podcast sample. Artist, album, track, playlist and show identifiers are not interchangeable.
These requests use your API key and can spend credits. Check the current price on the endpoint page; each new page is a separate request. Later examples use illustrative identifiers: replace them with values from your earlier response.
1. Discover an artist
Keep entity types and source IDs alongside names. Search does not guarantee a complete discography. Parameters and current cost →
curl "https://www.monocrawl.com/v1/spotify/search?query=Radiohead" \ -H "x-api-key: mn_your_key_here"
2. Resolve the artist
Replace the illustrative id with a returned artist ID. Audience counts and popularity are source metrics, not earnings or unique purchasers. Parameters and current cost →
curl "https://www.monocrawl.com/v1/spotify/artist?id=0cGUm45nv7Z6M6qdXYQGTX" \ -H "x-api-key: mn_your_key_here"
3. Inspect a known playlist
Use a playlist ID or URL you intend to inspect. Keep playlist order and any returned continuation rather than sorting all tracks by a popularity field. Parameters and current cost →
curl "https://www.monocrawl.com/v1/spotify/playlist?id=37i9dQZF1DXcBWIGoYBM5M" \ -H "x-api-key: mn_your_key_here"
Filters and coverage
Choose filters with the source behavior in mind
| Control | Behavior and limits |
|---|---|
| Identity | Store the entity type with the ID; an artist ID cannot be used as a track ID. Endpoint reference → |
| Market | Use only a declared market parameter. A missing field can reflect availability rather than a zero metric. Endpoint reference → |
| Collection bounds | Keep the returned order and continuation; impose a page and credit budget. Endpoint reference → |
Source availability, ordering and field coverage can change. Inspect warnings and partial-result metadata alongside the rows. See runnable workflows, metric semantics, computed fields and the pagination matrix.
Choose an endpoint
Match the operation to your task
| Your task | Endpoint | When to use it |
|---|---|---|
| A known album | album | Use an album ID or URL and a supported market when required by your use case. |
| A known track | track | Keep track and artist IDs separate. Missing playback information does not mean the track does not exist. |
| Podcast episodes | podcast/episodes | Resolve a podcast/show, then use its identifier and the episode endpoint’s own cursor and limit. |
Explore all documented operations by purpose below. Each endpoint reference contains its accepted parameters and current price.
Other operations
Posts and media
Search and discovery
Operations
Spotify
Each row is a registry operation: expand it for parameters, a curl built from the registry's own examples, and a Markdown copy of the whole entry. The badge on the right is the operation's state, read at request time — we publish all three rather than rounding up. Recorded proof is historical, not a guarantee of current availability.
- live · proven
- a real upstream response has been served through this API and recorded
- wired · unproven
- a real-data route is registered, but qualifying proof is absent; permission or capacity restrictions may apply
- sample · free
- no live upstream — /v1 refuses it, /sandbox returns a marked sample
Spotify
7 operationsElsewhere
The same registry, other shapes
- Spotify overview — supported data categories and use cases for this platform.
- Full endpoint reference — every platform on one page.
/openapi.jsonor/openapi.yaml— the machine-readable contract, for Postman, Insomnia or a client generator.GET /v1/utility/endpoints?platform=spotify— the same rows to your code at runtime, for 0 credits.