Scraping Social Media & App Stores
One REST request returns structured JSON from the App Store, Google Play, YouTube, Reddit, TikTok, X, Instagram, Facebook, and LinkedIn. Posts, videos, transcripts, comments, profiles, reviews, and job postings.
Scraping Social Media & App Stores
Chocodata now covers the social and app-store surfaces alongside the rest of the web. The same single GET you already use for e-commerce and search returns structured JSON for apps, videos, posts, profiles, and job listings:
GET https://api.chocodata.com/api/v1/{target}/{resource}?api_key=YOUR_KEY&...
No login, no session juggling, no per-platform SDK. Pass the identifier (an app ID, a video ID, a username, a post URL) and get back typed fields.
What you can pull
| Platform | {target} | Resources |
|---|---|---|
| Apple App Store | appstore | search, product, reviews |
| Google Play | googleplay | product, search |
| YouTube | youtube | video, channel, comments, transcript |
reddit | subreddit, post, user, search | |
| TikTok | tiktok | video, profile, oembed |
| X (Twitter) | xtwitter | tweet |
instagram | profile, post | |
facebook | page, post | |
linkedin | jobsearch, job, company |
A few highlights:
- App stores, both sides. Search a storefront, pull a single app’s full listing (price, version, ratings, genres, screenshots), and page through user reviews on the App Store, plus the Google Play equivalent.
- YouTube, including transcripts and comments. Beyond video metadata and channel uploads,
youtube.transcriptreturns the timed caption track as timestamped segments and one joined string, andyoutube.commentsreturns top or newest comments with author, like count, and reply count. - Reddit, with scores. Posts and comments carry their
score,upvote_ratio, andnum_comments, so you can rank and filter by engagement straight from the response. - TikTok, X, Instagram, Facebook, LinkedIn. Video and post detail with engagement stats, public profiles and company pages, and LinkedIn job search plus single-job detail.
A first call
curl "https://api.chocodata.com/api/v1/youtube/transcript?api_key=YOUR_KEY&video_id=dQw4w9WgXcQ"
{
"video_id": "dQw4w9WgXcQ",
"language": "en",
"is_generated": false,
"segment_count": 61,
"segments": [
{ "text": "♪ We're no strangers to love ♪", "start": 18640, "duration": 3240 }
],
"text": "♪ We're no strangers to love ♪ ♪ You know the rules and so do I ♪…"
}
The shape is the same one every Chocodata endpoint follows, so if you’ve used the Product or Search endpoints, these will feel familiar.
Per-endpoint reference
The full request shape, every parameter (with allowed enum values), and a real example response for each of these endpoints live in the endpoint reference:
- App Stores -
appstoreandgoogleplay. - Social Media -
reddit,youtube,tiktok,xtwitter,instagram,facebook, andlinkedin.
Related
- Endpoint reference - the resource model and every endpoint’s request/response.
- Product endpoint - the specific-item pattern these follow.
- Search endpoint - the list pattern.
- Getting started - your first scrape in two minutes.