Public social data, without the scraper upkeep.
Profiles, posts, comments, and transcripts from 12 platforms through one API. You send a handle or a link. We send back JSON that looks the same whether it came from TikTok or Reddit.
Want to talk it through first? Write to george@apidatahub.site. It goes to a person, not a ticket queue.
Try another tab. The platform changes, the fields don't.
Scrapers break. That's the whole problem.
If you've kept a scraper alive for more than a few months, you know how it goes. It runs fine for weeks. Then a platform changes its page layout on a Tuesday, and your pipeline quietly fills up with empty values until someone notices on Friday.
Now picture that for every platform your product touches.
We do that maintenance for you across twelve platforms and put a steady API in front of it. When something changes on a platform's side, we fix it on ours. Your code stays the same.
- One key and you're in. Put it in the
x-api-keyheader. No OAuth apps to register and no platform approval to wait on. - The same names everywhere.
followersmeans followers on every platform, and it's always a plain number, never "1.2M". - Read when you ask. Counts are fetched at request time, not copied from a crawl that ran last month.
- One way to page through lists. Every list comes back with
next_cursor. Send it back ascursoruntil it'snull.
The fields you'll use most
Every profile response starts with the same core fields, whatever the platform. Missing values come back as null rather than a missing key, and every timestamp is ISO 8601 in UTC.
Anything only one platform has, like TikTok's total likes or a YouTube channel's lifetime views, goes under platform_data. That way it never collides with the shared fields your code depends on.
| Field | Type | What it holds |
|---|---|---|
| platform | string | Where the data came from |
| handle | string | The public username |
| display_name | string | The name shown on the profile |
| verified | boolean | Whether the platform shows a badge |
| followers | integer | Followers or subscribers |
| posts_count | integer | Public posts or videos |
| bio | string | null | The profile description |
| links | string[] | Links listed on the profile |
| fetched_at | string | When we read it |
The platforms
Twelve platforms today, all on the same key. Here's what you can get from each.
- TikTokProfiles, videos, comments, transcripts, and search
- InstagramProfiles, posts and reels, comments, transcripts, and search
- YouTubeChannels, videos, shorts, comments, transcripts, and search
- XProfiles, posts, and search
- LinkedInProfiles, company pages, posts, and comments
- FacebookPublic pages, posts, and comments
- ThreadsProfiles, posts, and replies
- RedditSubreddits, posts, comment threads, and search
- PinterestProfiles, boards, pins, and search
- TwitchChannels, videos, clips, and transcripts
- BlueskyProfiles, posts, and replies
- SnapchatPublic profiles and Spotlight videos
Need a platform that isn't here? Tell us. Requests like that decide what we add next.
Your first request
It takes about five minutes, and most of that is waiting for the email.
- Ask for a key. Email george@apidatahub.site with a line about what you're building. You'll get a key to try things out.
- Make a call. Send a handle or a link along with your key. Any language that can make a web request will do.
- Use what comes back. Load it into your dashboard, your CRM, a spreadsheet, or an AI agent.
Pricing
Plans are based on how many calls you make. We don't publish a price list. Tell us which platforms you need and we'll quote a price that fits how you'll use it.
For getting a product off the ground or running a steady internal workflow.
- Every platform
- Email support
For a product that calls the API all day, every day.
- Every platform
- A lower price per call
- Faster replies when you need help
For larger volumes or anything that needs a custom setup.
- Volume pricing
- Custom data and fields
- Invoicing and an SLA
Questions people ask
What counts as public data?
Anything you can see in a browser without logging in: public profiles, public posts and their comments, public channel pages. We don't touch private accounts, direct messages, or anything behind a login.
What happens when a platform changes something?
We notice, we fix it on our side, and the response format you rely on stays the same. Honestly, that upkeep is most of what you're paying for.
How much does it cost?
There are three plans: 100,000 calls, 1 million calls, and Enterprise for anything bigger. We quote each one directly, so email us with which platforms you need and we'll come back with a price.
Can you add a platform or a field?
Often, yes. Email george@apidatahub.site with what you need and how you'd use it.
Can someone ask to have their data removed?
Yes. Anyone can email george@apidatahub.site to have their public data removed from our results and kept out of future ones.
Are you affiliated with any of these platforms?
No. We're an independent service that works only with publicly available information. Platform names are used to describe where the data comes from.
Tell us what you're building.
Send a couple of lines to george@apidatahub.site about your use case. We'll reply with a key and, if it helps, some ideas on where to start.