One header. Every endpoint.
Pass your key, call the endpoint, get structured data back — never a random HTML body to parse.
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 subscriptionNo credit card · From $1.65/1k at scale · PAYG credits never expire
Loading live API request countlive API requests · last 30 days API requests in the last 30 days
run one in the playgroundTeams 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
Under the hood
Auth, scraper upkeep, and billing — handled. Burst without rate-limit tickets. Explicit lookup outcomes — no charge for our infrastructure failures.
Pass your key, call the endpoint, get structured data back — never a random HTML body to parse.
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.
No per-minute cap, no rate-limit ticket. Set your own concurrency — we handle the throttling on our side.
No cache layer in the middle — the response reflects the account right now, not an hour ago.
Straight to the team behind the API — paste the request ID from a failing call and we trace it.
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
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.
Reliability
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.
99.8%
liveUptime
Measured across the public API over the last 90 days
~3.2s
live90-day avg response
Rolling mean latency on live upstream fetches — no cache in front
165
liveAPI endpoints
Profiles, media, search, and transcripts across every platform
21
livePlatforms
One API key across every supported network
Production workflows — one key, signed webhooks, research, and transcripts on typed endpoints.
Integration
REST or the TypeScript SDK — curl it from a shell, drop it in n8n, or call it from your job runner.
Copy your sf_live_… key from the dashboard — 100 free credits, no card. One key hits every platform route.
GET /v1/tiktok/profiles/{handle} with your key in the header. Platform lives in the path — not a generic /profile wrapper.
Every response includes meta.requestId and creditsCharged. Check lookupStatus before you write to your warehouse — retry a 503, not a not_found.
Also available
Capability modules for profiles, posts, search, and web — plus a Watch new items trigger — with your Social Fetch API key.
View guideVerified community node — drag HTTP Request blocks for profiles, search, and transcripts without hand-writing auth headers.
View guideRun Social Fetch from Apify Store with dataset export — pay per successful lookup, not per idle Actor minute.
View guideTyped client methods mirror every route — Result types, lookupStatus guards, and the same envelope as curl.
View guide165 endpoint tools with OAuth in Cursor, VS Code, and Claude — agents call typed routes instead of guessing at HTML.
View guidePoint at a profile, subreddit, or search — we poll on your schedule, diff results, and deliver a signed webhook when something new shows up. No cron job, no scraper upkeep.
View guidePay USDC per request on Base with no API key — agents and wallets hit the same endpoints as the credits rail.
View guideCustomer stories
“Our TikTok and Instagram scrapers broke constantly. Social Fetch took us off that rotation — we ship product again.”
“Transcripts at volume from one endpoint. No broken scrapers for our small team to maintain.”
“Live profile data on every request. We never flag accounts from a stale cache.”
“Heavy concurrent load, no rate limits to negotiate. The rare API I haven't wrapped in retries.”
Platforms
All 21 platforms and 165 endpoints — same catalog as docs and the playground.
TikTok
26 endpoints
Profile
GET/v1/tiktok/profiles/{handle}
Profile videos
GET/v1/tiktok/profiles/{handle}/videos
Profile followers
GET/v1/tiktok/profiles/{handle}/followers
Profile following
GET/v1/tiktok/profiles/{handle}/following
Profile region
GET/v1/tiktok/profiles/{handle}/region
Profile audience
GET/v1/tiktok/profiles/{handle}/audience
Live stream
GET/v1/tiktok/profiles/{handle}/live
Profile engagement
GET/v1/tiktok/profiles/{handle}/engagement
TikTok search
TikTok videos
TikTok Shop
Compare
One first-party API instead of DIY scrapers, generic scrape jobs, or marketplace actors.
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
100 free credits to start. PAYG packs never expire — or pick a monthly plan for steady volume.
100 free credits
1,000 credits
$14.00 / 1k requests
25,000 credits
$1.88 / 1k requests
230,000 credits
$1.64 / 1k requests
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.
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
No. Sign up for 100 free credits — no card required.
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.
No — PAYG packs work without a recurring plan. Starter, Growth, and Scale add included monthly credits; cancel anytime from billing.
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.
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.
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.
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.
Yes. Each request fetches publicly available data at request time (~3.2s avg) — not a stale cache.
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.
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.
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.
Yes. Versioned routes, predictable JSON, and operational signals — built for production pipelines, not demos.
Yes — as the social-data layer. Fetch normalized profiles, posts, metrics, comments, and transcripts, then apply your own scoring, verification, or valuation logic.
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.
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.
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.
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.
Monitoring, research, and enrichment on one API — no scraper maintenance.
Works across