All platformsLive Spotify data

Spotify data API. Any artist, album or track.

Artists, albums and tracks by id or share URL, as JSON in one request. No Spotify developer app and no OAuth.

No credit card requiredRead the API docs
  • No developer app
  • Share URLs or IDs
  • Failed lookups aren't charged
// Spotify artist — by id or share URL
const base = "https://api.socialfetch.dev";
const path = "/v1/spotify/artist";
const params = new URLSearchParams({
  artistId: "1uNFoZAHBGtllmzznpCI3s",
});

const res = await fetch(`${base}${path}?${params}`, {
  headers: { "x-api-key": "YOUR_API_KEY" },
});

const data = await res.json();
{
"displayName": "Justin Bieber",
"verified": true,
"followers": 90965890,
"monthlyListeners": 143198848,
"worldRank": 1,
// + 34 more — full schema in docs →
}
99.8% uptime#3 Product of the Day3,200+ developers

Teams running monitoring, research, and enrichment pipelines

We run the Spotify scrapers. You build the product.

Live Spotify data as JSON — proxies, platform changes and consistent output handled for you.

Spotify, plus every other network

One key and one response envelope for Spotify and 24 more platforms — profiles, posts, search, comments and transcripts.

Pricing you can reason about

One request, one credit. Know how far your balance will go before you run your next batch.

Live data on every request

Fetch public data when you ask for it — not from a shared cache.

No scraper maintenance

We handle proxies, browser changes, and platform breakages.

Built for production jobs

Run concurrent workloads with explicit statuses and request IDs.

Regular jobs. Better rates.

Running lookups every month? Get lower per-credit rates with a monthly plan. For occasional projects, choose pay as you go.

Never expires

What Spotify data can you get?

3 endpoints, one API key. Every response comes back as live JSON in the same envelope.

Browse all 3 Spotify endpoints
Use cases

What teams build with Spotify data

Monitoring, enrichment, research and content workflows on Spotify data — the same API as every other platform.

What you can build

Monitor brands and competitors

Find and vet creators

Check reach and engagement before you reach out.

Turn video into searchable text

Transcribe and index video and audio content so you can find the exact moment you need.

Track public communities

Follow the subreddits, groups, and channels where your audience talks.

How it works

Your first request in three steps.

Use TypeScript or your automation tool of choice.

Sources

+ 19 more platforms

One request

Social Fetch API

GET/v1/tiktok/profiles/charlidamelio

x-api-key: sk_live_••••••••

1 request · 1 credit

Same JSON shape

response.json200 OK
{
  "data": {
    "lookupStatus": "found",
    "profile": {
      "platform": "tiktok",
      "handle": "charlidamelio",
      "displayName": "charli d’amelio",
      "verified": true
    },
    "metrics": {
      "followers": 160263648
    }
  }
}
  1. Step 1

    Create your free account

    Get an API key with 100 requests included.

  2. Step 2

    Choose an endpoint

    Pass a username, URL, keyword, or post ID.

  3. Step 3

    Get clean JSON

    Use the response immediately or send it into your pipeline.

Works with your stack

Code, automate, or connect your AI.

Explore integrations

Pricing

Social data, priced simply.

Start with 100 free credits. Monthly plans give you predictable volume and lower per-request rates.

Starter

$29.00

18,000credits

  • Top up from $1.61 / 1k if you run out
  • Up to 25 monitors
Most popular

Growth

$79.00

50,000credits

  • Top up from $1.58 / 1k if you run out
  • 5 team seats
  • Up to 100 monitors

Scale

$225.00

150,000credits

  • Top up from $1.50 / 1k if you run out
  • 25 team seats
  • Up to 250 monitors
  • Cancel anytime
  • 30-day money-back guarantee
  • Price locked while you stay

Need 1M+ credits, invoicing, or volume rates? Talk to us

Trust signals

DevHunt

Product Hunt

Uneed

Customers

Teams building on Social Fetch.

“Our TikTok and Instagram scrapers broke constantly. Social Fetch took us off that rotation — we ship product again.”

Daniel Reeve · Founder, Social Crow
  • “Transcripts at volume from one endpoint. No broken scrapers for our small team to maintain.”

    Marcus Lin · Founder, Voice Gecko
  • “Live profile data on every request. We never flag accounts from a stale cache.”

    Hannah Webb · Founder, Scam Finder
  • “Heavy concurrent load, no rate limits to negotiate. The rare API I haven't wrapped in retries.”

    Owen Pritchard · Founder, IP Flare

Spotify API: common questions

Is there a Spotify scraper API / Spotify data API?

Yes. Social Fetch provides REST routes for public Spotify artists, albums, and tracks. Authenticate with a Social Fetch API key (x-api-key); you do not need a Spotify developer app for these public catalog lookups.

What Spotify data does Social Fetch cover?

Three operations under the Spotify tag: GET /v1/spotify/artist, GET /v1/spotify/album, and GET /v1/spotify/track. Artist responses can include metrics (followers, monthly listeners), related artists, and discography counts. Album responses include release metadata and an ordered tracklist. Track responses include title, duration, album context, and credited artists. Exact fields are on each endpoint page and in /docs/api.

Do I need a Spotify developer app or OAuth?

Not for Social Fetch public catalog routes. You only need a Social Fetch API key. Spotify Web API with a developer app and OAuth remains the path for playback, user libraries, and playlist write scopes.

Can I access user playlists or listening history?

No. These routes return public catalog metadata only. Private libraries, recently played, and playlists you manage require Spotify's official Web API with the appropriate user scopes.

What identifiers do Spotify routes accept?

Each route accepts either a Spotify entity id (artistId, albumId, or trackId) or a public https://open.spotify.com/... URL for that entity type. One identifier per request — do not send conflicting id and URL values on the same call.

How much does the Spotify API cost on Social Fetch?

You buy credit packs (or use the 100 free signup credits). Artist, album, and track lookups cost 1 credit each on a successful completed request. There is no required monthly subscription for pay-as-you-go packs. Always check meta.creditsCharged.

Spotify Web API vs Social Fetch — which should I use?

Use Spotify Web API when you need official quotas, playback, user-authorized features, or playlist management. Use Social Fetch when you want public artist/album/track enrichment without standing up a Spotify developer app, or when you already normalize social and music data through Social Fetch's shared envelope across platforms.

Does HTTP 200 always mean the artist, album, or track was found?

No. HTTP 200 means the request finished. Check data.lookupStatus: found means you got catalog data; not_found means the id or URL did not resolve. Persist meta.requestId when you need to debug a miss.

Can I use Spotify routes from agents or MCP?

Yes. The same operations appear as typed MCP tools and can be reached via Ask (POST /v1/ask) for plain-English exploration. For production jobs, pin the typed GET paths (/v1/spotify/artist, /album, /track) so routing stays explicit.

Is scraping Spotify data legal?

Social Fetch returns publicly visible catalog data. You are responsible for how you use it under Spotify's terms, applicable law, and your own compliance review. We do not give legal advice.

The Spotify API in detailHow the Spotify routes work, what they cost, and how they differ from the official API.

Why teams use Social Fetch for Spotify

Creator graphs often miss the Spotify artist ID behind a TikTok sound or pasted open.spotify.com link. Social Fetch exposes three GETs — artist, album, and track — by Spotify id or public URL. Every response uses { data, meta } with data.lookupStatus, meta.requestId, and meta.creditsCharged.

How to call the Spotify API

  1. 1. Create an API key

    Sign up at Social Fetch and copy a key (sfk_…). New accounts get 100 free credits — enough to smoke-test artist, album, and track GETs against live catalog data.

  2. 2. Call a Spotify route

    Send GET /v1/spotify/artist (or /album, /track) with x-api-key and either the entity id query param or a public Spotify URL. Use the TypeScript SDK or curl in production jobs; keep the playground for one-off checks in the app.

  3. 3. Join music ids to social rows

    Branch on data.lookupStatus before writing. Persist the Spotify artist/album/track id on the same person or campaign record as TikTok and YouTube handles. Log meta.requestId for support; bill from meta.creditsCharged.

What each Spotify route returns

  • Artist cards by Spotify artist id or artist URL — display name, bio, followers, monthly listeners, related artists, discography counts.
  • Album lookups with label, release date, cover art, credited artists, and an ordered tracklist.
  • Track metadata — title, duration, album context, credited artists — from a track id or share link.
  • Accept either a raw Spotify id or a public open.spotify.com/{artist|album|track}/… URL on each route.
  • Same Social Fetch API key and response envelope as TikTok, YouTube, Instagram, and the rest of the marketplace.

How much does the Spotify API cost?

Spotify artist, album, and track routes charge 1 credit per successful completed lookup. Credits never expire on pay-as-you-go packs. Confirm every response with meta.creditsCharged — that field is the billing source of truth.

Social Fetch vs the official Spotify API

Spotify Web API is for apps with developer credentials, rate limits, and user OAuth — playback, libraries, playlist management. Social Fetch routes are public catalog enrichment: id or URL in, JSON out, no Spotify developer app.

Pull your first Spotify data.

Run a live Spotify request in the playground. 100 free credits, no card, JSON back in seconds.

No credit cardSign up in 30 seconds withGoogleGitHub