Facebook Posts & Reels Scraper

Get the key public details from Facebook posts and reels — caption, views, reactions, comments, shares, publish date, and more — just by pasting links.

What you get

For each URL you provide, the actor returns one result with:

Field	Meaning
url	The link you pasted
finalUrl	The full Facebook page for that post/reel
postId	Facebook’s post / reel id
author	Page or profile name
pageHandle	Public username (when available)
caption	Post text
playCount	Views / plays
reactions	Reaction count
comments	Comment count
shares	Share count
durationSec	Video length in seconds
postDate	When it was published (UTC)
thumbnail	Preview image
status	ok if it worked, error if not
error	Short reason when something failed

Some fields can be empty (null) when Facebook doesn’t show them publicly.

How to use

1. Open the actor and paste your Facebook links into URLs — one link per line.
2. Leave Parallel workers at the default (16), or raise it for large batches (max 48).
3. Click Start.
4. Download results from the Dataset tab (JSON, CSV, Excel, etc.).

The URL input has no actor-imposed character limit. Apify's overall input size and your run's available memory still apply. Results appear in the dataset as each link finishes, in completion order, so you can inspect or export them during a run.

Workers reuse HTTP connections across links. Pending work, downloaded HTML, and outstanding dataset writes are bounded by worker count; completed rows are saved without keeping the entire batch in memory. Failed dataset writes fail the run.

Supported links

• Share links (facebook.com/share/r/…, share/p/…, share/v/…)
• Reels (facebook.com/reel/…)
• Watch / video links
• Public posts and permalinks

Example input

https://www.facebook.com/share/r/…
https://www.facebook.com/reel/…
https://www.facebook.com/watch/?v=…

Tips

• Use public posts and reels. Private or login-only content can’t be read.
• For big lists, start with the default workers; increase only if you’re comfortable with a higher request rate.
• Increasing Parallel workers can improve throughput when network waits dominate. Use more run memory with higher concurrency, and reduce workers if Facebook starts throttling requests.
• Thumbnail image links can expire after some time — save images you need soon after the run.
• Share counts of null usually mean Facebook didn’t expose the number publicly (not always “zero”).

Common results

Status	What it means
ok	Metadata extracted successfully
error + login_wall	Post requires login / isn’t public
error + empty_or_unresolved	Link couldn’t be opened or had no usable public data
error + not_a_facebook_url	The line wasn’t a Facebook link

Local checks

After installing requirements.txt, run python -m unittest discover -s tests -v. The tests use synthetic input and a local HTTP server, without calling Facebook or starting Apify runs.

Deployment

From this directory, with the Apify CLI signed in, run:

apify push plummy_bookbag/facebook-posts-links-scraper --build-tag latest

The command uploads the source and waits for the build. Tests stay in the project but are excluded from uploads by .actorignore. .gitignore excludes local environments, caches, storage, and credentials; .dockerignore keeps the Docker build context to runtime files.

Responsible use

This actor only collects information that is publicly visible on Facebook. Use the data in line with applicable laws, privacy rules, and Meta’s terms.