Retrieve Spotify browse section

Overview

Returns normalized items from Spotify's browseSection Pathfinder response for a Spotify section URI.

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

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

Response behavior

- Upstream token, app config, client token, or Pathfinder failures return `502`. - Items are normalized with title, subtitle, images, and external Spotify URLs when available. Example response: ```json { "code": 200, "msg": "OK", "data": { "uri": "spotify:section:0JQ5IMCbQBLqNPkcmYxQPQ", "offset": 0, "limit": 20, "items": [ { "uri": "spotify:playlist:example", "type": "Playlist", "title": "Example Playlist", "externalUrl": "https://open.spotify.com/playlist/example" } ], "meta": { "operationName": "browseSection", "count": 1, "fetchedAt": "2026-05-13T15:22:41Z" } } } ```

Error behavior

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

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

Related