Spotify Search API

Q: How do I search for artists or playlists instead of songs?

Set content_type to artists, albums, playlists or tracks. Each kind fills different fields, for example monthly_listener_count on artists and owner_name on playlists, so run one content_type per batch and keep the value with the rows you store.

Q: Can I search podcasts here?

Not with this capability; its content_type takes only the four music values. Podcasts have their own capability, Spotify Podcast, which searches shows or individual episodes with its own content type values. The two sets of values cannot be swapped between the capabilities.

Q: How do I get the full record for a result?

Pass the result's url to the capability for its kind: Spotify Track for tracks, Album for albums, Artist details for artists and Playlist for playlists. type on the row tells you which kind it is, which matters when you mix results from several searches.

POST

API health

24h health: Normal
24h average time: —

Healthy / normal
Available
Limited
Mostly down

Normal

Last 24 hours

Last 30 days

Search Spotify for tracks, artists, albums or playlists by keyword and get each match's name, type, artists and link, plus counts that fit the kind of result. Set the kind with content_type; results are not guaranteed to match across regions and do not show popularity over time.

Spotify Search finds tracks, artists, albums or playlists by keyword and returns each result's name, type, link, image and artists, plus fields that depend on the kind of result, such as album name, length, play count, followers, monthly listeners, track count, release date and playlist owner. Use it to find the exact Spotify object before you read it in full, to see what comes up for a theme or mood, or to build lists for playlist pitching and music research.

Choose the kind with content_type: tracks, artists, albums or playlists. duration_ms is in milliseconds, preview_url links to a 30-second preview and can be null, and is_explicit flags explicit content. Search results are a starting point; keep the url of the ones you want to read in full.

Price $1.39 per 1,000 requests ($0.001389 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.

AI prompt

Paste this into your AI assistant. It already holds this endpoint's parameters, response fields and an example request, so the assistant can ask what you need and then write the scraper.

Please help me write a data collection script with the EveryInfra Spotify Search endpoint (spotify/search).

Endpoint contract:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to spotify and action to search, and put the parameters inside params.
- Required parameters:
  - keyword: Specifies the search query for the search action, with target entities constrained by content_type.
- Optional parameters:
  - content_type: Filters target catalog types. For search, allowed values are tracks, artists, albums, or playlists. (allowed: albums / artists / playlists / tracks)
  - limit: The most rows to return in this call, an integer from 1 to 100. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 20)
- Returns a list of records. Main fields of each record: id, url, type, name, text, artists, album_name, owner_name, publisher, image_url, duration_ms, play_count; 20 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=spotify.
- Example request body:
{
  "platform": "spotify",
  "action": "search",
  "params": {
    "keyword": "arctic monkeys"
  }
}
- Price: $1.39 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.

Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.

Request parameters

Name	In	Type	Required	Default	Description
`Authorization`	header	`string`	Yes	-	Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
`platform`	body	`string`	Yes	`spotify`	Platform identifier, fixed value.
`action`	body	`string`	Yes	`search`	Capability identifier, fixed value.
`keyword`	body.params	Not declared	Yes	-	Specifies the search query for the search action, with target entities constrained by content_type. On the podcast action, this parameter searches overall podcast shows by default rather than looking up specific episode details.
`content_type`	body.params	`enum`	No	-	Filters target catalog types. For search, allowed values are tracks, artists, albums, or playlists. The podcast action takes its own values: podcasts_shows (default) for shows or podcast_episodes_individual_episodes for single episodes. Values from one action cannot be used in the other.Allowed values`albumsartistsplayliststracks`
`limit`	body.params	`integer (1–100)`	No	`20`	The most rows to return in this call, an integer from 1 to 100. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge.

Code samples

bash

curl -X POST 'https://api.everyinfra.com/api/v1/social' \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{
  "platform": "spotify",
  "action": "search",
  "params": {
    "keyword": "arctic monkeys"
  }
}'

[OpenAPI definition (JSON)]Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

Real response

Captured September 26, 2026 at 08:56 (UTC) by calling this API with the parameters in the code sample above. results and count are that call's real response with personal information (names, handles, avatars, profile links, contact details) removed; the list keeps the first 2. id, billing and quota differ on every call, so only their shape is shown.

json

{
  "id": "req_…",
  "platform": "spotify",
  "action": "search",
  "results": [
    {
      "id": "5XeFesFbtLpXzIVDNQP22n",
      "url": "https://open.spotify.com/track/5XeFesFbtLpXzIVDNQP22n",
      "type": "track",
      "name": "I Wanna Be Yours",
      "artists": [
        "Arctic Monkeys"
      ],
      "album_name": "AM",
      "image_url": "https://i.scdn.co/image/ab67616d0000b2734ae1c4c5c45aabe565499163",
      "duration_ms": 183956,
      "is_explicit": false,
      "platform": "spotify"
    },
    {
      "id": "5FVd6KXrgO9B3JPmC8OPst",
      "url": "https://open.spotify.com/track/5FVd6KXrgO9B3JPmC8OPst",
      "type": "track",
      "name": "Do I Wanna Know?",
      "artists": [
        "Arctic Monkeys"
      ],
      "album_name": "AM",
      "image_url": "https://i.scdn.co/image/ab67616d0000b2734ae1c4c5c45aabe565499163",
      "duration_ms": 272394,
      "is_explicit": false,
      "platform": "spotify"
    }
  ],
  "count": 20,
  "billing": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}

Response fields

Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.

Field	Meaning
`id`	The record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms.
`url`	Link to the record on the platform.
`type`	Record type; values depend on the capability (for example video / image / text).
`name`	Name of the object itself, for account, product and business capabilities.
`text`	Body text with HTML removed, returned in full and never cut short (on a few platforms the list results themselves carry only an excerpt; the platform's field notes say so).
`artists`	Keeps the platform's own meaning
`album_name`	Keeps the platform's own meaning
`owner_name`	Keeps the platform's own meaning
`publisher`	Keeps the platform's own meaning
`image_url`	Image link. Capabilities with several images may return an image_urls array.
`duration_ms`	Keeps the platform's own meaning
`play_count`	Keeps the platform's own meaning
`follower_count`	Followers. null means not disclosed, not 0.
`monthly_listener_count`	Keeps the platform's own meaning
`track_count`	Keeps the platform's own meaning
`episode_count`	Keeps the platform's own meaning
`release_date`	Keeps the platform's own meaning
`is_explicit`	Keeps the platform's own meaning
`preview_url`	Keeps the platform's own meaning
`rank`	Keeps the platform's own meaning
`platform`	Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).

FAQ

How do I search for artists or playlists instead of songs?

Set content_type to artists, albums, playlists or tracks. Each kind fills different fields, for example monthly_listener_count on artists and owner_name on playlists, so run one content_type per batch and keep the value with the rows you store.

Can I search podcasts here?

Not with this capability; its content_type takes only the four music values. Podcasts have their own capability, Spotify Podcast, which searches shows or individual episodes with its own content type values. The two sets of values cannot be swapped between the capabilities.

How do I get the full record for a result?

Pass the result's url to the capability for its kind: Spotify Track for tracks, Album for albums, Artist details for artists and Playlist for playlists. type on the row tells you which kind it is, which matters when you mix results from several searches.

Errors and billing

401: Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.
422: Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.
402: Insufficient balance. Top up first.
429: The account's per-minute request limit was reached (all of its API keys count together; a key's own lower limit applies first). Wait for Retry-After and try again; a rate package in the console raises the limit.
503: Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.
200 empty: The request completed without data and is not charged (billing.reason = empty_result_refunded).