Extract public Facebook data — Page profiles, posts and reels, reviews and ratings, public group activity, and Ad Library creatives — as structured JSON, on demand or on a schedule.
The Facebook Scraper API resolves public Pages, posts, reels, reviews, and the Ad Library. Hand us a Page URL, post permalink, or search query and we return profile metadata, engagement metrics, comment threads, and media — clean and validated.
Used by brand-monitoring, social-intelligence, and competitive-ad-research teams that need dependable public Facebook data without managing sessions or proxies. Ad Library coverage exposes active creatives, spend ranges, and run dates for political and commercial advertisers.
# POST a target — get validated JSON back
curl https://api.crawlzo.com/v4/scrape \
-H "Authorization: Bearer $CRAWLZO_KEY" \
-d '{
"url": "https://www.facebook.com/MetaAI",
"type": "page",
"include": "recent_posts,reviews"
}'
// ← response
{
"status": "ok",
"data": {
"page_name": "Meta AI",
"category": "Software company",
"likes": 1820400,
"followers": 1904220,
"rating": 4.3,
"recent_posts": [
{ "id": "…", "reactions": 8421, "comments": 332, "shares": 190 }
]
}
} "type": "page",
"include": "recent_posts,reviews"Facebook data parsed into clean, validated JSON. Pull any group below on its own, or combine them in a single request.
Brand and reputation monitoring
Competitive ad research via Ad Library
Social listening and crisis detection
Local-business review intelligence
Yes. Query by advertiser, Page, or keyword and we return active creatives, the running Page, spend and impression ranges where Facebook discloses them, run dates, and the platforms each ad runs on.
No. We extract public data only — public Pages, public posts, public reviews, public group activity, and the Ad Library. Private profiles and closed groups are out of scope by policy.
Structured JSON straight from the API, or pushed to your stack natively — S3, BigQuery, Snowflake, Postgres, Kafka, or any HTTPS webhook. Call it from Python, Node, Go, Rust, or any HTTP client. The data lands where your pipeline already lives.
No. You pay for valid, schema-passing rows only. Retries, blocks, CAPTCHAs, and 5xxs are on us. If a run doesn't return data that conforms to the schema, it isn't billed.
Every request routes through the same engine behind our Web Unblocker API: compliant residential IPs, real browser fingerprints, TLS-level evasion, behaviour modelling, and built-in CAPTCHA solving. Hard targets become routine.
Yes. We respect robots policies, rate budgets, and ToS-aware allow/deny lists. We deliver and move on — no row-level retention beyond your replay window. GDPR DPA, PII redaction, and custom data residency available on request.