Profiles, posts, transcripts, and metrics from 13+ platforms — live on every request. Consistent fields you can trust in production pipelines. We maintain the scrapers. 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
Live profile fields you can store — followers, bio, verification — without babysitting Instagram scrapers.
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 predictable billing — handled. Burst without negotiating rate limits. Explicit lookup outcomes you can trust in pipelines — and we never charge you for our infrastructure failures.
Pass your key, call the endpoint, get structured data back — never a random HTML body to parse.
$ curl https://api.socialfetch.dev/v1/instagram/profiles/zuck \-H "x-api-key: YOUR_KEY"
import { SocialFetchClient } from "@socialfetch/sdk"const client = new SocialFetchClient({apiKey: process.env.SOCIALFETCH_API_KEY})const result = await client.instagram.getProfile({handle: "zuck"})if (result.ok) console.log(result.value.data)
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, auth changes, and schema drift so your team ships roadmap instead of patching selectors. Boring infrastructure, interesting products on top.
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
150+
liveAPI endpoints
Profiles, media, search, and transcripts across every platform
13
livePlatforms
One API key across every supported network
Workflows we see in production — one key across platforms, monitoring, 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
Verified 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 guide
Typed client methods mirror every route — Result types, lookupStatus guards, and the same envelope as curl.
View guide87 endpoint tools with OAuth in Cursor, VS Code, and Claude — agents call typed routes instead of guessing at HTML.
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.”
15+Developer Integrations Built
99.8% uptime~3.2s avg response
Compare
DIY scrapers break on every layout change. Marketplace actors mean another publisher, another queue, and another monthly fee. Social Fetch is first-party: live lookups on one key, credits that never expire, and optional monthly plans when volume is steady.
| Feature | Social Fetch | Build Your Own | General Scraping APIs | API Marketplaces |
|---|---|---|---|---|
Live upstream fetch (not a shared cache) Fresh profile and post data on each completed lookup | ||||
13+ platforms on one API key TikTok, Instagram, YouTube, LinkedIn, Reddit, and more on one balance | ||||
No published per-minute cap on paid routes Spend credits at the pace your job needs | ||||
Zero scraping maintenance on your side We handle selectors, proxies, and upstream breakage | ||||
Pay-as-you-go with no required subscription No recurring tier just to keep marketplace listings active | ||||
PAYG credits never expire Buy a pack once; use it across months or burst days — separate from subscription included credits | ||||
Support with `requestId` from every response One vendor to paste an ID to — not a marketplace ticket chain | ||||
Versioned fields when platforms change Documented breaking changes instead of silent data drift in your pipelines |
Side-by-side write-ups with pricing scenarios and honest trade-offs for Apify, Bright Data, EnsembleData, and RapidAPI.
Pricing
Start with 100 free credits. Pay-as-you-go packs never expire — or pick a monthly plan when volume is steady. Need 1M+ credits? Talk to sales.
100 free credits
1,000 credits
$14.00 / 1k requests
25,000 credits
$1.88 / 1k requests
230,000 credits
$1.64 / 1k requests
1M+ credits
Volume rates
Every tier includes all platform APIs. Pricing FAQ below covers credits, billing, subscriptions, and top-ups.
FAQ
No credit card required. Sign up and receive 100 free credits instantly—start making real API calls in minutes with no payment information needed.
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 — pay-as-you-go credit packs work without a recurring plan. Starter, Growth, and Scale subscriptions are available when you want included credits each month at a lower effective rate; cancel anytime from billing with no penalty.
Yes. A completed lookup costs credits whether the target exists or not—a wrong username that returns lookupStatus: not_found still ran a real lookup. lookup_failed and 503 temporarily_unavailable are not charged.
No enforced rate limits or RPS caps on paid metered routes—your limit is credit balance. Stay below ~500 concurrent requests for best 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.
Around 3.2 seconds on average. Because Social Fetch fetches live data from each platform on every request (no caching), responses take a little longer than a static API — and in return you always get fresh data, not yesterday's snapshot.
Yes. Every request fetches the latest publicly available data from the platform at request time — typically in around 3.2 seconds — so your product always reflects what's live instead of 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, LinkedIn, YouTube, X (Twitter), Threads, Reddit, Rumble, Telegram, Spotify, and GitHub — plus Web routes for generic URL tasks. See the capability matrix for the full route list.
Yes. The API is designed for production SaaS: predictable JSON shapes, versioned routes, and operational focus so your team ships features instead of maintaining scrapers.
Yes. Social Fetch is a strong fit for the social-data layer: fetch normalized public profiles, posts, metrics, comments, transcripts, and engagement signals, then apply your own weighting, scoring, verification, or valuation logic in your app.
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.
Join teams running monitoring, research, and enrichment on one API — without owning brittle scrapers.
Works across
