> **For coding agents and LLMs:** This is one Social Fetch marketing page (markdown export). For API orientation start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for auth and crawl rules use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for every operation use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt). ## This page - **On-site (HTML):** - **Markdown (.mdx) URL:** --- # What is a social media scraper API? A social media scraper API fetches public social pages, parses them into structured fields, and returns JSON over HTTP. You pay per lookup instead of running browsers, proxies, and parsers yourself. ## What's actually on offer Range from general scraping runtimes (you write extraction logic) to vertical public-data APIs with normalized schemas (Social Fetch) — you never touch HTML. Both solve: public pages aren't machine-readable, layouts change, and fetch infrastructure is ongoing ops work. ## How access works Social Fetch: sfk_… via x-api-key, { data, meta } envelope, data.lookupStatus on 200. Also @socialfetch/sdk or hosted MCP (OAuth). ## What a lookup actually returns Daily competitor dashboard: DIY = headless browser, proxies, DOM selectors that break on redesign. Scraper API = GET profile + video-list routes, typed JSON, meta.creditsCharged. DIY: full control, ongoing maintenance. Maintained API: stable schema, limited to documented fields. ## Vs building it yourself DIY: you own proxies, fingerprints, CAPTCHAs, selector breakage. Reasonable for unusual extraction or low volume. Maintained API: someone else absorbs layout changes — better once you need multiple platforms and predictable costs. ## Common mistakes Assuming all "scraper APIs" are async browser jobs — some are typed REST like Social Fetch. Public visibility ≠ compliance for every use case — maintained API changes who runs the pipeline, not your obligations. Retrying not_found doubles the charge without changing the answer. ## What Social Fetch does not do Public data only — no private/login-gated accounts, no guaranteed refresh cadence beyond per-route docs. Credit pricing: Starter $14/1k, Growth $59/25k, Scale $379/230k. 100 free credits on signup. See /pricing. ## FAQ ### What is a social media scraper API? Hosted fetch + structured JSON over HTTP. Some are general runtimes; Social Fetch is typed REST with normalized schemas. ### Is web scraping legal for social media data? Depends on jurisdiction, platform terms, and use case — not legal advice. API changes who runs the pipeline, not your compliance obligations. ### How is a scraper API different from an official platform API? Official: first-party, partner approval, owner-scoped data. Public-data/scraper APIs: public content at scale, third-party product. ### Do empty or private results still cost credits? Yes on Social Fetch — completed lookups including not_found/private bill. lookup_failed and 503 don't. ### Why not just run my own scraper with Puppeteer or Playwright? You can — full control at the cost of proxy rotation and parser maintenance on every layout change. ### Does a scraper API have rate limits? Social Fetch: no published RPS cap on paid routes; credits are the limit. Free whoami/balance have separate limits. ### How much does a social media scraper API cost? Social Fetch PAYG from $14/1k credits, cheaper at higher tiers. 100 free on signup. ### Can I access private or login-gated social accounts? No. Public content visible without logging in only. ## Related - [Social Fetch homepage](https://www.socialfetch.dev/) - [Compare hub](https://www.socialfetch.dev/compare) - [Platforms](https://www.socialfetch.dev/platforms) - [Credits docs](https://www.socialfetch.dev/docs/credits) - [Free tools](https://www.socialfetch.dev/tools) - [Social media API](https://www.socialfetch.dev/glossary/social-media-api) - [Lookup status](https://www.socialfetch.dev/glossary/lookup-status) - [Public social data](https://www.socialfetch.dev/glossary/public-social-data) - [API credits](https://www.socialfetch.dev/glossary/api-credits)