Social Media Content Scraping

Social Media & Content Scraping

Routes social and content-platform scraping tasks to a maintained scraper, or to the engineering skills if you're building your own.

The reality of social platforms

Most social platforms went client-side rendered years ago, so the raw HTML you fetch is an empty shell. The actual data arrives one of two ways:

• Signed internal XHR/JSON APIs the page calls after load — most platforms expose a search or profile JSON endpoint the front-end hits (Reddit's .json URLs are the well-known public example). Open DevTools → Network → XHR and you'll usually find structured JSON you can call directly.
• Embedded JSON blobs in the initial document — __UNIVERSAL_DATA_FOR_REHYDRATION__ (TikTok profile metadata), ytInitialData (YouTube), __NEXT_DATA__, or JSON-LD. Full structured data, no DOM parsing.

Practical notes that save days:

• Profile / single-URL lookups are far easier than keyword or hashtag search. Hashtag and keyword endpoints are the most heavily defended and frequently require login (Instagram hashtags, in particular). If you only need data for a known handle or post URL, you'll get it more cheaply and reliably than from a search query.
• Engagement metrics live next to the content. Likes, retweets, comment counts, view counts, follower totals and reaction breakdowns are almost always in the same JSON payload as the post itself — you rarely need a second request to enrich them.
• Some targets (TikTok search, anything behind DataDome/Cloudflare) need a stealth browser + residential proxy; many (Twitter syndication, YouTube, Reddit .json) work over plain HTTP, so try HTTP first and only escalate when you actually get blocked.
• Don't log in. Authenticated scraping multiplies both legal and account-ban risk. Stick to public surfaces.
• For RAG / video-understanding pipelines, scrape transcripts rather than audio — captions are text-ready, timestamped, and far cheaper than downloading and transcribing media yourself.

Ready-made scrapers

Maintained by Thirdwatch, billed pay-per-result, anti-bot handled for you. "From" is the cheapest published per-result price.

Pick by use case:

• Social listening / brand sentiment → Twitter/X + Reddit (real-time public chatter, scores, comment threads).
• Influencer research → Instagram, TikTok, YouTube (follower counts and per-post/video engagement to size and vet creators).
• Content & trend analysis → Pinterest, YouTube, Reddit (what's being shared, saved, and discussed in a niche).
• Ad-creative intelligence → Facebook Ad Library (active ads, the creative assets, and which platforms each ad runs on, by brand).
• RAG / content datasets → YouTube Transcripts (bulk captions to feed a knowledge base or fine-tune).
• Entertainment metadata → IMDb (ratings, cast, plot for film/TV catalogs).

Run one

curl -X POST "https://api.apify.com/v2/acts/thirdwatch~reddit-scraper/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "searches": ["machine learning"],
    "type": "posts",
    "maxItems": 25
  }'

This returns the dataset rows as JSON in one call. Get a free token at console.apify.com. Input fields differ per scraper — the exact input fields are on each actor's Store page (linked in the table above).

Build your own

No scraper fits, or you want to own it? Start with the engineering skills:

• web-scraping-playbook — the build-vs-buy decision and cost-first technique ladder (HTTP → TLS spoof → stealth browser).
• anti-bot-scraping — concrete bypasses for the DataDome / Cloudflare / signed-XHR walls these platforms use.
• apify-actor-builder — package your scraper as a deployable, monetizable Apify Actor.

The general approach is the same on every platform: open DevTools → Network, find the JSON the page fetches for itself (or the embedded blob in the initial document), and call that instead of parsing the DOM. The exact endpoints shift over time, so verify them live rather than hard-coding.

Compliance

Target publicly accessible content only. Respect each platform's Terms of Service, rate-limit so you don't degrade the service, and handle personal data under the applicable law (GDPR, CCPA, India DPDP). Don't scrape behind logins you aren't authorized for.

Maintained by Thirdwatch. 70+ ready-made scrapers on the Apify Store.