Docs menu

Spotify API endpoint

Retrieve Spotify public profile playlists

Returns normalized public playlists from Spotify's Web Player user-profile service. Provide username, uri, or url; defaults to Spotify's official profile.

GETapiKey3 credits/requestSpotifyspotify.userProfilePlaylistsResponseDoc/spotify/profile/playlists

Overview

Returns normalized public playlists from Spotify's Web Player user-profile service. Provide username, uri, or url; defaults to Spotify's official profile.

Request schema

NameInTypeRequiredEnumExampleDescription
usernamequerystringNospotifySpotify username
uriquerystringNospotify:user:spotifySpotify user URI
urlquerystringNohttps://open.spotify.com/user/spotifyopen.spotify.com user URL
offsetqueryintegerNo0Playlist offset
limitqueryintegerNo20Playlist limit, clamped to 1-50
x-api-keyheaderstringYesAPI key required

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost
3 credits/request
Charged response
Successful 2xx responses
PlanPriceIncluded creditsDaily capRate limitOverage
Free$0/mo2,000500 daily credits5/minNo overage
Starter$9/mo20,0005,000 daily credits15/min$0.75/1,000 overage credits when enabled
Growth$29/mo100,00025,000 daily credits45/min$0.45/1,000 overage credits when enabled
Pro$79/mo400,000No daily cap120/min$0.30/1,000 overage credits
Business$199/mo1,200,000No daily cap300/min$0.20/1,000 overage credits
Enterprise$499/mo5,000,000No daily cap1,000/min$0.12/1,000 overage credits

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

  • Proxy strategy: managed automatically where needed
  • Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
  • Browser cluster: supported dynamic workloads can be routed through distributed browser instances
  • Retry behavior: automatic retry/fallback may be used depending on endpoint type
  • Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
  • Billing: credits are charged only for successful 2xx responses
  • Observability: responses include request context where available

MCP

MCP URL
https://mcp.crawlora.net/mcp
Tool name
spotify.profile_playlists
Transport
Streamable HTTP
Docs resource
docs://index

Response behavior

The endpoint uses the public Web Player profile playlist service with anonymous Spotify credentials.

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

StatusCommon failure case
400Invalid input or missing required parameter
429Plan or endpoint rate limit exceeded
500Internal execution error
502Upstream platform failed, returned unusable HTML, or served a challenge page that could not be resolved

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Failure responses

StatusDescriptionSchema
400Missing or invalid parameters#/definitions/app.Response
429Rate limit exceeded#/definitions/app.Response
502Spotify upstream request failed#/definitions/app.Response

Example response

{
  "uri": "spotify:user:spotify",
  "username": "spotify",
  "offset": 0,
  "limit": 20,
  "totalPublicPlaylistsCount": 1519,
  "publicPlaylists": [
    {
      "uri": "spotify:playlist:37i9dQZF1DXcBWIGoYBM5M",
      "name": "Today’s Top Hits",
      "followersCount": 34324513
    }
  ]
}

Request schema

No body schema

Response schema

#/definitions/spotify.userProfilePlaylistsResponseDoc

FieldTypeRequiredEnumBoundsExampleDescription
codeintegerNoCode is the HTTP status code or a custom code used to indicate the result of the request @example 200
dataspotify.UserProfilePlaylistsResponseNo
data.limitintegerNo20
data.metaspotify.UserProfileMetaNo
data.meta.appVersionstringNo1.2.90.403.gf901f20f
data.meta.artistCountintegerNo0
data.meta.fetchedAtstringNo2026-05-13T20:41:12Z
data.meta.operationNamestringNouserProfileView
data.meta.playlistCountintegerNo10
data.meta.profileCountintegerNo50
data.offsetintegerNo0
data.publicPlaylistsarrayNo
data.publicPlaylists[].externalUrlstringNohttps://open.spotify.com/playlist/37i9dQZF1DXcBWIGoYBM5M
data.publicPlaylists[].followersCountintegerNo34324513
data.publicPlaylists[].idstringNo37i9dQZF1DXcBWIGoYBM5M
data.publicPlaylists[].imageUrlstringNohttps://i.scdn.co/image/ab67706f0000000273f7bb6e77ec5e23d7840ae5
data.publicPlaylists[].isFollowingbooleanNofalse
data.publicPlaylists[].namestringNoToday’s Top Hits
data.publicPlaylists[].ownerNamestringNoSpotify
data.publicPlaylists[].ownerUristringNospotify:user:spotify
data.publicPlaylists[].ownerUrlstringNohttps://open.spotify.com/user/spotify
data.publicPlaylists[].ownerUsernamestringNospotify
data.publicPlaylists[].uristringNospotify:playlist:37i9dQZF1DXcBWIGoYBM5M
data.totalPublicPlaylistsCountintegerNo1519
data.uristringNospotify:user:spotify
data.usernamestringNospotify
msgunknownNoMsg is the message that describes the result of the request @example "Request successful"

Code examples

Use environment variables for secrets and keep Crawlora API keys server-side.

curl -X GET "https://api.crawlora.net/api/v1/spotify/profile/playlists?username=spotify&uri=spotify%3Auser%3Aspotify&url=https%3A%2F%2Fopen.spotify.com%2Fuser%2Fspotify&offset=0&limit=20" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Responsible public web data workflows

Crawlora is designed for responsible structured public web data workflows. Customers are responsible for using Crawlora in compliance with applicable laws, third-party rights, target-platform rules, and Crawlora terms.

Read Crawlora terms

Related