Spotify API endpoint
Use Crawlora's Spotify profile followers API to extract supported public Spotify data as structured JSON. This page includes request parameters, cURL examples, response schema, error behavior, credit cost, and a Playground link for testing before integration.
/spotify/profile/followersReturns normalized public follower profiles from Spotify's Web Player user-profile service. Spotify exposes this as a public anonymous response for some profiles; private or restricted profiles may return an upstream error. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and AI-agent workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.
Request parameters are generated from the active endpoint catalog. Required values must be sent before Crawlora can call the upstream public web data source.
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| username | string | No | Spotify username | spotify | |
| uri | string | No | Spotify user URI | spotify:user:spotify | |
| url | string | No | open.spotify.com user URL | https://open.spotify.com/user/spotify | |
| offset | integer | No | Follower offset applied locally | 0 | |
| limit | integer | No | Follower limit, clamped to 1-200 | 50 | |
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/spotify/profile/followers?username=spotify&uri=spotify%3Auser%3Aspotify&url=https%3A%2F%2Fopen.spotify.com%2Fuser%2Fspotify&offset=0&limit=50" \ -H "x-api-key: $CRAWLORA_API_KEY"
Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.
Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.
| Plan | Price | Included credits | Daily cap | Rate limit | Overage |
|---|---|---|---|---|---|
| Free | $0/mo | 2,000 | 500 daily credits | 5/min | No overage |
| Starter | $9/mo | 20,000 | 5,000 daily credits | 15/min | $0.75/1,000 overage credits when enabled |
| Growth | $29/mo | 100,000 | 25,000 daily credits | 45/min | $0.45/1,000 overage credits when enabled |
| Pro | $79/mo | 400,000 | No daily cap | 120/min | $0.30/1,000 overage credits |
| Business | $199/mo | 1,200,000 | No daily cap | 300/min | $0.20/1,000 overage credits |
| Enterprise | $499/mo | 5,000,000 | No daily cap | 1,000/min | $0.12/1,000 overage credits |
This endpoint is executed through Crawlora's managed scraping infrastructure.
Spotify exposes public followers anonymously for some profiles. Private or restricted profiles may return an upstream error.
Crawlora does not silently return bad data when the upstream page cannot be used.
| Status | Common failure case |
|---|---|
| 400 | Invalid input or missing required parameter |
| 429 | Plan or endpoint rate limit exceeded |
| 500 | Internal execution error |
| 502 | Upstream 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.
| Status | Description | Schema |
|---|---|---|
| 400 | Missing or invalid parameters | #/definitions/app.Response |
| 429 | Rate limit exceeded | #/definitions/app.Response |
| 503 | Spotify upstream request failed | #/definitions/app.Response |
{
"uri": "spotify:user:spotify",
"username": "spotify",
"offset": 0,
"limit": 50,
"total": 998,
"profiles": [
{
"uri": "spotify:user:example",
"username": "example",
"name": "Example"
}
]
}Request schema
No body schema
Response schema
#/definitions/spotify.userProfileFollowersResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | Code is the HTTP status code or a custom code used to indicate the result of the request @example 200 | |||
| data | spotify.UserProfileFollowersResponse | No | ||||
| data.limit | integer | No | 50 | |||
| data.meta | spotify.UserProfileMeta | No | ||||
| data.meta.appVersion | string | No | 1.2.90.403.gf901f20f | |||
| data.meta.artistCount | integer | No | 0 | |||
| data.meta.fetchedAt | string | No | 2026-05-13T20:41:12Z | |||
| data.meta.operationName | string | No | userProfileView | |||
| data.meta.playlistCount | integer | No | 10 | |||
| data.meta.profileCount | integer | No | 50 | |||
| data.offset | integer | No | 0 | |||
| data.profiles | array | No | ||||
| data.profiles[].color | integer | No | 16085920 | |||
| data.profiles[].externalUrl | string | No | https://open.spotify.com/user/example | |||
| data.profiles[].followersCount | integer | No | 1000 | |||
| data.profiles[].imageUrl | string | No | https://i.scdn.co/image/ab6775700000ee8555c25988a6ac314394d3fbf5 | |||
| data.profiles[].isFollowing | boolean | No | false | |||
| data.profiles[].name | string | No | Example | |||
| data.profiles[].uri | string | No | spotify:user:example | |||
| data.profiles[].username | string | No | example | |||
| data.total | integer | No | 998 | |||
| data.uri | string | No | spotify:user:spotify | |||
| data.username | string | No | spotify | |||
| msg | unknown | No | Msg is the message that describes the result of the request @example "Request successful" |
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/spotify/profile/followers?username=spotify&uri=spotify%3Auser%3Aspotify&url=https%3A%2F%2Fopen.spotify.com%2Fuser%2Fspotify&offset=0&limit=50" \
-H "x-api-key: $CRAWLORA_API_KEY"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