Docs menu
Spotify API endpoint
Retrieve Spotify public profile followers
Returns 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.
/spotify/profile/followersOverview
Returns 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.
Request schema
| Name | In | Type | Required | Enum | Example | Description |
|---|---|---|---|---|---|---|
| username | query | string | No | spotify | Spotify username | |
| uri | query | string | No | spotify:user:spotify | Spotify user URI | |
| url | query | string | No | https://open.spotify.com/user/spotify | open.spotify.com user URL | |
| offset | query | integer | No | 0 | Follower offset applied locally | |
| limit | query | integer | No | 50 | Follower limit, clamped to 1-200 | |
| x-api-key | header | string | Yes | API 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
| 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 |
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_followers
- Transport
- Streamable HTTP
- Docs resource
- docs://index
Response behavior
Spotify exposes public followers anonymously for some profiles. Private or restricted profiles may return an upstream error.
Error behavior
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.
Failure responses
| Status | Description | Schema |
|---|---|---|
| 400 | Missing or invalid parameters | #/definitions/app.Response |
| 429 | Rate limit exceeded | #/definitions/app.Response |
| 502 | Spotify upstream request failed | #/definitions/app.Response |
Example 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" |
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/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"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