
Social Fetch
Scraper API for TikTok, Instagram, YouTube, X & LinkedIn
I run a small bussiness that pulls social media data. Follower counts, video stats, engagement ect. From the start I handled the scraping myself. Proxies, session management, dealing with platforms changing things every other week.
It worked fine for a while. Then something would break, I'd spend all day fixing it, when I should be focusing on marketing.
I figured, I'm not the only person dealing with this. Anyone building social media tools, analytics dashboards, influencer platforms, content trackers — has this exact same problem. The scraping isn't their business either. It's just a thing that needs to work so they can get on with what actually matters.
So I built Social Fetch. One API, 8 platforms (Instagram, TikTok, YouTube, X, Threads, Pinterest, Snapchat, Reddit), consistent response format. Hit an endpoint, get your data, move on with your life.
2 months in:
312 users
121K+ requests served
~1,500/day right now
Under 3 second average response time
Most used: TikTok video data and Instagram posts
The users are pretty much exactly who I expected. People building tools where social data is an input, not the output. Nobody's here because they can't figure out web scraping. They're here because they figured out it's not worth their time.
It's at socialfetch.dev. Would genuinely appreciate feedback from anyone building in this space. What's missing, what would make it more useful, what would get you to switch from whatever you're currently doing.
About
I got tired of maintaining scrapers for my own social media tools. Proxies, broken sessions, wasted days fixing things instead of building. Others have the same problem, so I built the solution I wished existed.

1 Comment
"The scraping isn't their business either, it's just a thing that needs to work so they can get on with what actually matters." That line, plus "social data is an input, not the output," is the sharpest positioning in this whole post, and none of it is on your homepage.
Your site leads with "Social media scraper API for every major platform," which names the mechanism. This post names the relief, and relief is what people pay for. You also have the origin every dev believes on sight: you lost days fixing scrapers when you should have been marketing.
You asked what would make someone switch, so here is one answer: put this post on the homepage. Lead with "get your data and move on with your life," keep "scraper API" in the title tag for search, and let the platform count be proof rather than the pitch.
Was the category-descriptor headline a deliberate search play, or just the safe default?