

Facebook Post Scraper extracts post content and engagement data from Facebook by visiting individual post URLs. It fetches each post page concurrently and parses the text content, media attachments, reactions, comments, shares, and other metadata.
Facebook Post Scraper extracts post content and engagement data from Facebook by visiting individual post URLs. It fetches each post page concurrently and parses the text content, media attachments, reactions, comments, shares, and other metadata.
Facebook Post Scraper can gather the following data from each post:
| 📝 Post content | 🆔 Post ID | 📅 Date posted |
| 👤 User name | 🌐 User URL | ✅ Page verified |
| 💬 Comments count | 🔁 Shares count | 👍 Likes count |
| 😍 Reaction types | 🖼️ Post images | 🎬 Attachments |
| 🔗 Hashtags | 📺 Video views | 📰 Post type |
| 💰 Is sponsored | 🤝 Sponsor name | 📷 Avatar image |
Facebook Post Scraper is easy to use. Follow these 5 steps:
https://www.facebook.com/zuck/posts/10102593740125791).url field.retry_times and max_concurrency if needed.To start scraping Facebook posts, fill in the input parameters. Facebook Post Scraper supports the following inputs:
3)8)Each input URL returns one result row:
| Field | Type | Description |
|---|---|---|
url | string | The post URL that was crawled |
status | string | Collection status (success or failed) |
data | object | Parsed post content data |
error | string | Error message (empty on success) |
error_code | string | Error code (empty on success) |
Here is an example of the data object in JSON:
When the scraper cannot retrieve data for a given URL, it pushes an error item to the dataset instead of silently skipping it. Normal output items are never affected; you can tell them apart by the presence of a non-empty error_code field.
error_code | Meaning |
|---|---|
PAGE_NOT_FOUND | The requested post URL does not exist or has been removed |
ACCESS_DENIED | The post is private or requires login |
REQUEST_TIMEOUT | The request timed out after all retry attempts |
PARSE_ERROR | The HTML response could not be parsed |
NETWORK_ERROR | A network-level error occurred during fetching |
Facebook Post Scraper supports standard posts (with text, images, or links) and video posts/Reels. The post_type field in the output indicates whether a post is a Post or Reel.
Yes. The url field accepts an array of post URLs. The scraper will process all URLs concurrently and return one result row per URL.
The scraper uses concurrent requests (controlled by max_concurrency) to fetch multiple post pages in parallel. With the default setting of 8 concurrent requests, it can process a large batch of URLs efficiently. You can increase max_concurrency up to 20 for faster scraping.
For video posts, the scraper extracts additional fields such as video_view_count and play_count. Media attachments will contain video URLs, thumbnails, and video duration.
The scraper returns an error item with a PAGE_NOT_FOUND error code for deleted posts, while continuing to process the remaining URLs normally.
Explore more popular scrapers from our marketplace
by CoreClaw
Extract data in real time via URLs, easily capture posts, shares and engagement metrics, free from complex infrastructure maintenance and IP blocks. One-click CSV/JSON export supported.
by CoreClaw
Extract public Facebook event data in bulk via URLs, including details, attendance and organizer info. One-click CSV/JSON export, no coding required.
by CoreClaw
Scrape Facebook profiles by inputting a profile URL, including basic user information, work experience, education background, contact information, etc., and output them in CSV or JSON format.
by CoreClaw
Extract public Facebook event data in bulk from event list URLs, including basic info, organizer and participant data. Export CSV/JSON with one click, no coding required.