Facebook Pages Scraper

What does Facebook Pages Scraper do?

Facebook Pages Scraper helps you extract public data from Facebook Pages using a page URL, handle, or numeric page ID. It can collect posts, photos, reviews, reels, videos, future events, past events, and page details from one or more Facebook pages in a single run.

You can run it directly on Apify, export results via API, schedule recurring runs, connect it to automation tools, and monitor runs from one place. It is designed for teams that need page data in a structured format without building and maintaining their own Facebook page scraping workflow.

Why use Facebook Pages Scraper?

Facebook page data is useful for market research, local business monitoring, social media tracking, and lead enrichment. This Actor helps you collect public page activity and metadata in a format that is easier to analyze than browsing pages manually.

Common use cases:

• Track new posts published by restaurants, stores, venues, and brands.
• Collect public reviews and recommendation signals for reputation analysis.
• Monitor reels and videos published by competitor or partner pages.
• Export page details such as follower counts, contact details, categories, and website links.
• Keep an eye on upcoming or past events posted by public Facebook pages.

Because it runs on Apify, you also get scheduling, API access, integrations, run history, monitoring, and dataset export in multiple formats.

How to use Facebook Pages Scraper

1. Open the Actor on Apify and go to the Input tab.
2. Add one or more Facebook page references into the urls field.
3. Use a full page URL like https://www.facebook.com/copperkettleyqr/, a handle like copperkettleyqr, or a numeric page ID.
4. Choose the data type you want to extract: posts, photos, videos, reels, reviews, future events, past events, or page details.
5. If you selected posts, optionally set startDate and endDate in YYYY-MM-DD format.
6. Set maxResults if you want to limit results per page, or enable parseAllResults to paginate until no more data is available.
7. Start the Actor and wait for the run to finish.
8. Open the Storage tab to inspect the dataset, or export it as JSON, CSV, Excel, XML, or HTML.

Input

Configure the Actor in the Input tab. The current input supports these main fields:

• urls: One or more Facebook page URLs, handles, or numeric page IDs.
• type: The page resource to extract.
• maxResults: Maximum number of items to save per page when pagination is limited.
• parseAllResults: When enabled, the Actor keeps paginating until no more results are available.
• startDate: Optional lower date bound for post collection.
• endDate: Optional upper date bound for post collection.

Notes:

• startDate and endDate only apply when type is set to posts.
• If both dates are provided, startDate must be earlier than or equal to endDate.
• Some resource types require a page URL or handle rather than a numeric ID, because the Actor first resolves extra page-level metadata before collecting the final results.
• Personal profiles and Facebook groups are not supported by this Actor.

Example input:

{
  "urls": [
    "https://www.facebook.com/copperkettleyqr/",
    "copperkettleyqr"
  ],
  "type": "posts",
  "maxResults": 100,
  "parseAllResults": false,
  "startDate": "2026-05-01",
  "endDate": "2026-05-15"
}

Output

The Actor stores results in the default Apify dataset. The output structure depends on the selected type.

Example output for posts:

{
  "post_id": "1371481031662792",
  "type": "post",
  "url": "https://www.facebook.com/copperkettleyqr/posts/...",
  "message": "Our classic turkey dinner is now available for a limited time.",
  "timestamp": 1775309548,
  "comments_count": 0,
  "reactions_count": 3,
  "reshare_count": 0,
  "author": {
    "id": "100064027242849",
    "name": "The Copper Kettle Restaurant",
    "url": "https://www.facebook.com/copperkettleyqr"
  }
}

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

Data table

Below are some of the main fields the Actor can return across supported page resource types:

Field	Description
page_id	Facebook page ID
name	Page or event name
url	Public URL of the page, post, event, reel, or video
post_id	Post or review identifier
video_id	Reel or video identifier
message	Post or review text
description	Reel or video description
timestamp	Unix timestamp of the item
comments_count	Number of comments
reactions_count	Number of reactions
reshare_count	Number of reshares
play_count	Number of plays for reels or videos
followers	Page follower count
verified	Whether the page is verified
categories	Page categories
services	Services listed on the page
event_place.location	Event location text

Pricing / Cost estimation

How much does it cost to scrape Facebook page data?

The cost depends mainly on:

• How many page references you provide
• Which type you select
• Whether you enable parseAllResults
• How many pages of results are available for each Facebook page

Small runs that fetch page details or a limited number of posts are usually inexpensive. Larger runs that paginate deeply through posts, reels, videos, or events will consume more platform resources. If you want predictable costs, set maxResults and keep parseAllResults disabled.

Tips and advanced options

• Use full page URLs when possible for the clearest input.
• Use maxResults during testing so you can validate the output shape quickly.
• Enable parseAllResults only when you truly need the complete archive available from the selected endpoint.
• When scraping posts within a time window, provide both startDate and endDate to reduce unnecessary pagination.
• If you need regular monitoring, schedule the Actor to run automatically and connect the dataset to your downstream workflow.

FAQ, disclaimers, and support

Does this Actor scrape personal profiles?

No. It is intended for supported public Facebook Pages only.

Does it support multiple pages in one run?

Yes. The Actor processes page references one by one and stores all results in the same dataset.

Can I use a page handle instead of a full URL?

Yes. Handles such as copperkettleyqr are supported.

Is it legal to scrape Facebook page data?

You are responsible for using this Actor in compliance with applicable laws, website terms, and the rules of your use case. Only collect and use data you are allowed to process.

What if a page returns fewer items than expected?

That can happen when the page has limited public content, the selected resource type is sparse, or pagination reaches the end of available results.

If you need help or want a custom version, use the Issues tab on the Actor page or request a tailored solution for your workflow.