3.6M lookups · 30 days

Social media scraper API for every major platform.

Profiles, posts, transcripts, and metrics from 21 platforms — live on every request, consistent fields, scrapers maintained for you. Social scrape without running browsers yourself. 100 free credits, no card.

Sign up in 30 seconds withGoogleGitHubDiscord

No credit card · Live data · No required subscription

// Instagram profile
const base = "https://api.socialfetch.dev";
const path = "/v1/instagram/profiles/charlidamelio";

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

const data = await res.json();
{
"handle": "charlidamelio",
"displayName": "Charli D'Amelio",
"followers": 48300000,
"following": 1284,
"verified": true,
"bio": "don't worry i won't post a lot",
"avatarUrl": "https://instagram.fcdn.net/...",
// + 22 more — full schema in docs →
}

Loading live API request countlive API requests · last 30 days

run one in the playground

Teams running monitoring, research, and enrichment pipelines

"Our TikTok and Instagram scrapers broke constantly—proxies, rewrites, the works. Social Fetch let us get back to building." Social Crow

99.8% uptime#3 Product of the Day3,200+ developers

Designed so your team ships features, not glue code

Auth, scraper upkeep, and billing — handled. Burst without rate-limit tickets. Explicit lookup outcomes — no charge for our infrastructure failures.

One header. Every endpoint.

Pass your key, call the endpoint, get structured data back — never a random HTML body to parse.

Pricing you can reason about

Pay-as-you-go credits — no required subscription, no expiry on packs. Optional monthly plans when volume is steady. We eat the cost of our own lookup_failed errors — you don't.

request1
credit1

Burst without negotiating

No per-minute cap, no rate-limit ticket. Set your own concurrency — we handle the throttling on our side.

Always fetched fresh

No cache layer in the middle — the response reflects the account right now, not an hour ago.

~3.2savg response
live · last 30 days

Answers from someone who built it

Straight to the team behind the API — paste the request ID from a failing call and we trace it.

U

Why's my TikTok handle returning 404?

9:42

Region block on our side — fixed. Your req_07d1…eede_pg trace shows the upstream 503; not charged.

9:47

Credits don't rot on a shelf

Buy once, burn them in your burst windows, go quiet when the job's done. No reset date, no pressure — they just don't expire.

never_expirespay_as_you_gono_lock_in
credit usage over timeno reset date
buy 25k
use when you need
still here
today+2 years →

Reliability

Engineers off the scraper on-call rotation

We absorb DOM shifts and schema drift so your team ships product, not selectors.

Read the reliability page — measured uptime, live fetch, no fake SLAs.

No charge when we break

Infrastructure failures don't touch your balance. You pay for completed lookups, not our scraper having a bad hour.

requestId on every call

Paste it into support and we trace the exact upstream attempt. No back-and-forth about what happened at 2 a.m.

lookupStatus before you parse

Found or not_found, always explicit — never an empty array you have to guess about.

Consistent data you can trust

Stable field meanings across platforms and versioned changes when upstream shifts — so pipelines don't silently skew.

All systems operational
  • 99.8%

    live

    Uptime

    Measured across the public API over the last 90 days

  • ~3.2s

    live

    90-day avg response

    Rolling mean latency on live upstream fetches — no cache in front

  • 165

    live

    API endpoints

    Profiles, media, search, and transcripts across every platform

  • 21

    live

    Platforms

    One API key across every supported network

What you can build
4 use cases

Ship without babysitting scrapers

Production workflows — one key, signed webhooks, research, and transcripts on typed endpoints.

Integration

API key to production in an afternoon

REST or the TypeScript SDK — curl it from a shell, drop it in n8n, or call it from your job runner.

  1. Step 01

    Get your API key

    Copy your sf_live_… key from the dashboard — 100 free credits, no card. One key hits every platform route.

  2. Step 02

    Call an endpoint

    GET /v1/tiktok/profiles/{handle} with your key in the header. Platform lives in the path — not a generic /profile wrapper.

  3. Step 03

    Know what succeeded before you store

    Every response includes meta.requestId and creditsCharged. Check lookupStatus before you write to your warehouse — retry a 503, not a not_found.

Customer stories

Teams shipping 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

Platform highlights

What you get

Profiles, posts, and engagement in one shape

Drop in curl, Python, or the TypeScript SDK

15+Developer Integrations Built

99.8% uptime~3.2s avg response

Client reports from one key

Platforms

Every platform in one place

All 21 platforms and 165 endpoints — same catalog as docs and the playground.

Compare

Social Fetch vs. the alternatives

One first-party API instead of DIY scrapers, generic scrape jobs, or marketplace actors.

Feature
DIY
Scrapers
Markets
  • Live upstream fetch

  • 21 platforms, one API key

  • No published rate caps

  • Zero scraping maintenance

  • Pay-as-you-go, no required plan

  • Credits that never expire

Side-by-side write-ups with pricing scenarios and real trade-offs

Pricing

Pricing that scales with your jobs.

100 free credits to start. PAYG packs never expire — or pick a monthly plan for steady volume.

Free

$0.00no card

100 free credits

  • Real endpoints — not a sandbox with fake JSON
  • Same API as paid plans
  • No card on signup

Starter

$14.00one-time

1,000 credits

  • Prove one workflow before you buy more
  • All 21 platforms on one API key
  • Up to 5 active monitors
  • Credits never expire — spend them when you need them
  • No subscription required
Most popular

Growth

$47.00one-time

25,000 credits

  • For a project or one-off batch job
  • Better per-credit rate than the Starter pack
  • All 21 platforms on one API key
  • Up to 5 active monitors
  • Credits never expire — spend them when you need them

Scale

$379.00one-time

230,000 credits

  • For a large one-time job, not a monthly plan
  • Best pack rate of the three — includes bonus credits
  • All 21 platforms on one API key
  • Up to 5 active monitors
  • Credits never expire — no subscription required

How credits work

Pay-as-you-go packs never expire

One-time purchases. Buy today, spend next year — your PAYG balance is kept separately and is always preserved.

Subscription credits reset monthly

Included credits reset each period and do not roll over. Overflow draws from your PAYG balance first, then your tier's prepaid refill pack.

Cancelling never forfeits PAYG credits

Cancel at period end from billing. Included credits stay until the period closes; your pay-as-you-go balance is never forfeited.

Read the full credits guide

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

Every tier includes all platforms. FAQ below covers credits, billing, subscriptions, and top-ups.Pricing FAQ

FAQ

Common questions

Do I need a credit card to get started?

No. Sign up for 100 free credits — no card required.

Do credits expire?

Pay-as-you-go pack credits never expire — buy once and use them on your schedule. Subscription included credits reset each monthly period; unused included credits do not roll over. Refill-pack credits land in your PAYG balance and never expire.

Do I need a subscription?

No — PAYG packs work without a recurring plan. Starter, Growth, and Scale add included monthly credits; cancel anytime from billing.

Do not_found lookups cost credits?

Yes. Completed lookups charge whether the target exists or not — `lookupStatus: not_found` still ran upstream. `lookup_failed` and `503 temporarily_unavailable` are not charged.

Are there rate limits?

No RPS cap on paid metered routes — credit balance is the limit. Stay below ~500 concurrent requests for reliability. `whoami` and `balance` have per-key limits. Retry `503 temporarily_unavailable` with backoff.

Do you offer team or workspace accounts?

Not today. Each account has one billing owner. Teams often share an API key with their own internal controls, or contact us for enterprise arrangements.

What is the average response time?

About 3.2 seconds on average. Each request fetches live from the platform — no cache — so responses are slower than a static API but always current.

Is the data real-time?

Yes. Each request fetches publicly available data at request time (~3.2s avg) — not a stale cache.

What's your uptime?

We currently run at 99.8% uptime measured across the public API over the last 90 days. If you ever hit an issue, every response includes a request ID you can send to support@socialfetch.dev.

Which platforms are supported?

TikTok, Facebook, Instagram, Pinterest, LinkedIn, YouTube, X (Twitter), Threads, Bluesky, Reddit, Rumble, Twitch, Telegram, Spotify, GitHub, Google Ad Library, and Web routes for generic URL tasks. See the capability matrix for the full route list.

What are Monitors?

Watch a public profile, subreddit, or search on a schedule and get a signed webhook when something new posts — Social Fetch runs the poll and diff; you write the handler. See /monitoring for the product overview and /docs/monitors/quickstart to go live.

Can we use this in production?

Yes. Versioned routes, predictable JSON, and operational signals — built for production pipelines, not demos.

Can Social Fetch support profile enrichment, valuation, or scoring workflows?

Yes — as the social-data layer. Fetch normalized profiles, posts, metrics, comments, and transcripts, then apply your own scoring, verification, or valuation logic.

What about compliance?

Social Fetch returns publicly available data. You are responsible for how you use it under your contracts, platform terms, and applicable law. We are operated by Social Freak Ltd (UK). See our Security and Privacy pages for data handling, retention, and GDPR rights.

Are you SOC 2 or ISO 27001 certified?

No. We do not hold SOC 2 or ISO 27001 certification. See our Security page for our current practices (TLS, optional 2FA, approximately 30-day API logs). For enterprise security questionnaires, email support@socialfetch.dev.

Do you support GDPR?

We are designed to support UK and EU GDPR rights — this is our privacy practice, not a third-party certification programme. See our Privacy page for legal bases, retention, and how to contact us. Email support@socialfetch.dev for data subject requests.

Who are your subprocessors?

Public documentation describes generic categories (hosting, payments, email, analytics). Stripe processes payments. A detailed subprocessor list is available on request for legitimate security reviews — email support@socialfetch.dev.

Run your first live lookups in minutes

Monitoring, research, and enrichment on one API — no scraper maintenance.

Works across

TikTokTwitterFacebookRedditYouTubeInstagramTelegramLinktree+ more