About Social Fetch
We build a unified API for public social data so engineering teams can stop maintaining scrapers and get back to shipping product. One integration, every network, predictable JSON.
Every team that touches social media ends up writing the same thing: bespoke scrapers for each platform, maintained indefinitely by whoever drew the short straw. One platform update and someone is triaging incidents on a Saturday. We've been that team.
Public social data should behave like any other API—consistent schemas, predictable errors, changelogs you can plan around. The data already exists. What's missing is a layer that normalises it, absorbs upstream churn, and lets your team move on.
Social Fetch provides REST endpoints for profiles, posts, media, search, and engagement data across 20+ networks. Same field names across TikTok, Instagram, YouTube, and the rest. Adding a new network usually means changing a query parameter, not rewriting an integration.
What we optimise for
Not a mission-statement wall—things you'll actually notice when you integrate, read the docs, or open a support ticket.
Clarity over cleverness
Every field is documented. Every error has a code. You should know what a field means six months from now without reading source.
Operational honesty
When platforms change upstream, we tell you what changed, when, and what to update. No silent breakage.
Developer-led roadmap
Features get built when real teams hit real walls. We read support threads before sprint planning.
Stable contracts
Schema changes are versioned, documented, and announced. You pick when to migrate—not us.
Security and scope
We work with publicly available data. If a use case is in a grey area, email us before building—not after.
No artificial friction
No rate limits, no per-minute caps, no lock-in subscriptions. Pay for credits; use them when you need them.
How we work
We keep the team intentionally small, so nobody sits between you and the engineers shipping fixes. When you open a support ticket, the person replying is usually the same person who wrote the endpoint.
Docs come first, support second, sales last. We'd rather you never need to contact us because the docs answered the question. When you do, you get a direct reply—not a ticket number and a 72-hour SLA.
Want to collaborate, challenge a use case, or ask whether something is in scope? Email us—we reply to every message. If you're ready to build, start with the quickstart.