subimpact WhatsApp us

Facebook Posts Scraper alternative: subimpact Pages Scraper

Both actors read public Facebook Pages without a login and return posts with text, publish time, reactions, comments, shares and media links. apify/facebook-posts-scraper lists $5.00 per 1,000 posts on the Free plan and $2.00 per 1,000 on Gold, plus a start fee. Ours lists $1.00 per 1,000 posts, with page rows at $2.00 per 1,000 and comments at $0.50 per 1,000, and no start fee. Theirs adds per reaction breakdowns and video transcripts; ours adds page and comment rows. Both run on the Apify Store.

Prices checked 20 Nov 2026. Both actors run on Apify, so the numbers come from the same Store listing pages.

Key facts side by side

Fact Facebook Posts Scraper This API (Facebook Pages Scraper: Posts, Pages & Comments)
Price per 1,000 posts (Free plan) $5.00 $1.00
Higher plans (Gold) $2.00 $1.00
Start fee per run $0.001 None
Platform usage Included Included
Users on the Apify Store 144,982 17
Rating 4.7 (236 reviews) No reviews yet
Last build 16 Nov 2026 20 Nov 2026
Pricing model Pay per event Pay per event

Apify Store list prices, checked 20 Nov 2026. Platform usage 'Paid separately' means Apify bills compute on top of the event price.

Head-to-head test

10 latest posts from the NASA Facebook page

Measure Facebook Posts Scraper This API
Status SUCCEEDED SUCCEEDED
Items returned 10 10
Run time (seconds) 7.8 6.3
Average filled fields per item 29.0 15.0
Distinct fields 34 30
List price of the job $0.051 $0.01
Measured platform usage $0.00 of compute, included in the price $0.00024 of compute, included in the price

One run each on 20 Nov 2026, same input, default memory. Small samples; your results will vary with input.

Which one to choose

When to choose Facebook Posts Scraper

  • You need a breakdown per reaction type rather than totals.
  • You want video transcripts and shared post details in the same row.
  • You want the actor with the largest run history in this lane.
  • You rely on date filters for posts newer or older than a date.

When to choose this API

  • You want page profile rows and recent posts from the same actor.
  • You need the visible comments of a post in the same dataset.
  • You want no start fee before the first post is delivered.
  • You prefer one row shape with a rowType field for pages, posts and comments.

Switching from Facebook Posts Scraper

Their input field Our input field Note
startUrls pageUrls Page links go into pageUrls; a single post, video, reel or photo permalink goes into postUrls instead.
resultsLimit maxPostsPerPage Same idea of a cap on delivered items, here set per page, with maxItems as a run wide ceiling.
onlyPostsNewerThan (none) No date filter input; the actor delivers the latest posts and you filter on createdAt.
onlyPostsOlderThan (none) No older than filter; facebook.com serves the latest posts only to logged out requests either way.
captionText (none) No transcript option; text is the post caption or body as published.

Example input

{
  "pageUrls": [
    "https://www.facebook.com/NASA",
    "https://www.facebook.com/bbcnews"
  ],
  "maxPostsPerPage": 20,
  "includeComments": true,
  "maxCommentsPerPost": 20,
  "maxItems": 200,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}

Actor id: subimpact/facebook-pages-scraper. Paste the input above into the Apify Console and press Start.

Where each one is stronger

Where Facebook Posts Scraper is stronger

  • Larger user base and a long review history on the Apify Store
  • Per-reaction breakdowns, video transcripts and shared post details
  • Optional date filters on published posts

Where this API is stronger

  • Comments are available in the same run, priced per comment
  • Page profile rows with follower and about fields come from the same actor
  • No actor start fee before the first post is delivered

Questions people ask

How do the prices compare per 1,000 posts?

apify lists $5.00 per 1,000 posts on the Free plan and $2.00 per 1,000 on Gold, plus a $0.001 start fee and an optional date filter add-on. Ours lists $1.00 per 1,000 posts, $2.00 per 1,000 page rows and $0.50 per 1,000 comments, with platform usage included and no start fee.

Does the output shape carry over?

Partly. Our rows use postId, postUrl, text, createdAt, reactions, comments, shares, videoViews and imageUrls, with rowType telling pages, posts and comments apart. The per reaction fields such as reactionLoveCount, the transcript and the sharedPost block have no counterpart, so any code that reads those needs a change.

Do I need Facebook cookies or a login?

No. The actor makes plain HTTP requests to facebook.com as a logged out visitor, so there are no cookies and no browser. That also sets the ceiling: private pages, groups and personal profiles are out of reach, and only what facebook.com shows to a logged out visitor comes back.

How many posts can I get from one page?

About 20, which is what facebook.com serves to a logged out request. maxPostsPerPage accepts 0 to 50, but asking for more does not fetch older posts because there is no deeper pagination. Set it to 0 when you only want the page row and its follower counts.

Can I collect comments in the same run?

Yes, for single post links. Add the post permalink to postUrls with includeComments on and the comments the post page renders are delivered as their own rows at $0.0005 each, which is $0.50 per 1,000. There are no further comment pages, so the number of comment rows can be lower than the post's comment count.

How do I switch over from their actor?

Move your page links from startUrls into pageUrls, put anything that was set in resultsLimit into maxPostsPerPage, and drop the date filters, which have no equivalent. Then check the fields your pipeline reads against our column names before scheduling the first production run.

What happens when a page is login gated?

The row comes back with status not_found_or_login_wall and is not charged. On the default proxy the actor retries on fresh sessions and then once through a residential proxy, because facebook.com sometimes refuses datacenter addresses for public pages, and the error column says which case applied.

Need a data source that is not here?

We build and run scrapers for sites that have no public API. Tell us the site, the fields and how often you need them.