Social media APIs
Pull live profiles, posts, audiences, transcripts, and search across X, GitHub, YouTube, Instagram, TikTok, and Reddit — then turn a handle into a contactable person.
Social media APIs
We built these APIs so you can work with what people actually post and who they follow, not just a static B2B snapshot. Search a topic, pull a profile, page through an audience, read the comments, or read a transcript.
Two of these platforms go further than data. On X and GitHub, a public handle converts into a LinkedIn URL, and from there Contact Reveal gets you an email. That is the motion most tools stop short of: they show you the post, we get you to the person.
Platforms
X (Twitter)
Profiles, keyword search, followers, tweets, replies, quotes, retweeters — plus handle → LinkedIn.
GitHub
GitHub username → LinkedIn and work emails, and LinkedIn or a name → GitHub.
YouTube
Channels, video metadata, timestamped transcripts, comments, and search.
Creator and brand profiles, posts, Reels, and post comments.
TikTok
Creators, search, transcripts, trending feeds, follower lists, and sounds.
Global keyword search, subreddit feeds, and threaded comments.
How these calls behave
Platform data endpoints — profiles, posts, search, audiences, transcripts, comments — are synchronous request/response calls. You send a handle, a URL, or a query and you get the answer back.
Identity matching is split. Two lookups are synchronous:
| Direction | Operation | Shape |
|---|---|---|
| X handle → LinkedIn | twitterHandleToLinkedinUrl | Sync, one call |
| GitHub username → LinkedIn | githubToLinkedinSingle | Sync, one call |
Everything else is a background job — you call a trigger, get a run ID, and either poll or take a webhook. That covers GitHub batches, LinkedIn → GitHub, and person → X / Instagram. Even the single-person social lookup is a job. Expect the first poll to still be running.
There is no Instagram, TikTok, YouTube, or Reddit handle → LinkedIn lookup. Those platforms are pseudonymous enough that the bridge runs the other way: start from a person and find their profile.
Pagination
Two conventions, and mixing them up is the most common integration bug here.
| Platform | Response field | Send back as |
|---|---|---|
| X (Twitter) | nextCursor | cursor |
| YouTube, Instagram, TikTok, Reddit | nextPageToken | nextPageToken |
A null value means there are no more pages. Omit the field entirely on the first request.
Using them effectively
Decide your stopping condition before you start paging. List endpoints bill per page, so a follower sweep on a large account has no natural end and no natural cost ceiling. Set a page cap in the job.
Go narrow before you go wide. Search finds where a conversation lives; that is cheap. Profiles, transcripts, and audience walks are where the credits go, so spend them only on the accounts and posts that survived the search.
Prefer the engaged over the numerous. The people who replied to a post, commented on a Reel, or quote-tweeted a launch are a smaller and much warmer list than an entire follower graph, and they cost less to collect.
Batch identity lookups instead of looping singles. On GitHub the batch route is several times cheaper per person than the single, not just faster.
Read chargeInfo, not the price list. Every response reports what that
specific call cost. It is authoritative when the two disagree.
Reach for Tracker when you want to be told. These APIs are one-shot pulls. Continuous watching of companies and people is Tracker.
Use cases
Work intent while it is still fresh. Search X or Reddit for the language people use when your problem bites, resolve the X handles to LinkedIn, reveal the email, and reach out the same day. The Reddit half gives you the wording even when it cannot give you the person.
Source developers who never update LinkedIn. Take contributors or stargazers from a relevant repository, batch them through GitHub → LinkedIn, and enrich the matches. Their code is current even when their profile is not.
Run creator and influencer sourcing end to end. Discover on TikTok with hashtags and sounds, verify reach and engagement on Instagram, and read what they actually say on YouTube before you commit budget.
Track brand and competitor conversation across networks. Mentions on X, threads on Reddit, reviews on YouTube, and reactions on TikTok answer different halves of the same question. Turn the engaged commenters into a list.
Credits
Social data calls cost 2 credits each — per request on single-object
routes, per page of results on lists. Identity matching is priced per lookup
and varies by direction: see X and
GitHub for exact numbers. Polling a background job
is free. chargeInfo on every response is authoritative — see
Billing & credits.
Related: Contact Reveal · Webhooks · Tracker
Exclusion lists
Keep customers, competitors, and past contacts out of every search — free lists of companies or people that filter your results automatically.
X (Twitter)
X profiles, keyword search, follower graphs, and tweet-level engagement — plus a synchronous handle-to-LinkedIn lookup that makes an X identity contactable.