Facebook Pages + Posts Scraper

Collect public Facebook Page identity, contact, post, media, and engagement data without stitching separate exports together.

Scrape Facebook Pages and posts together. Extract Page details, contacts, followers, captions, reactions, comments, shares, photos, videos, reels, links, and engagement data. Supports Page URLs, direct posts, mixed lists, date filters, and optional encrypted cookies.

All examples below use fictional DEMO-* identifiers, reserved .test domains, and masked contact details. They do not represent real people, listings, products, or companies.

🚀 What this Actor does

• Flexible collection: PAGES_AND_POSTS, PAGES_ONLY, POSTS_ONLY, DIRECT_POSTS.
• Structured output: clean JSON records organized into pages, posts, media, contacts, all views.
• Production-ready: concurrency, retries, proxy support, limits, and source-aware diagnostics are exposed through the Actor input.
• Easy automation: run from the Apify Console, API, schedules, webhooks, Make, Zapier, or any HTTP client.

🎛️ Modes and workflows

Mode or workflow	What it does
PAGES_AND_POSTS	Return Page identity plus recent posts for every Page input.
PAGES_ONLY	Collect Page profile, audience, contact, cover, and category data.
POSTS_ONLY	Collect posts reached through Page inputs.
DIRECT_POSTS	Resolve exact public post, Reel, photo, or video URLs.

💡 Common use cases

• Public Page directories and lead research
• Content and engagement analysis
• Media, contact, and campaign monitoring

📥 Input schema

Configure the Actor in the Input tab or send the same JSON through the API. Fields not needed for your workflow can be omitted.

Field	Type	Description	Default
startUrls	array	Add Facebook Page, profile, post, photo, video, reel, or fb.watch URLs. Pages + Posts mode automatically handles mixed URL lists.	—
scrapeType	string	Pages + Posts is the universal default. Focused modes are useful when you need only one record type. Allowed: PAGES_AND_POSTS, PAGES_ONLY, POSTS_ONLY, DIRECT_POSTS.	PAGES_AND_POSTS
maxPostsPerPage	integer	Maximum matching posts saved for each Page URL. Direct post URLs always return at most one post.	20
startDate	string	Optional earliest publication date in YYYY-MM-DD format, for example 2026-01-01.	—
endDate	string	Optional latest publication date in YYYY-MM-DD format.	—
captionText	string	Optional case-insensitive text filter for post captions.	``
maxItems	integer	Hard run-wide limit across Page and post rows. The Actor stops saving and requesting more data after this limit or the maximum charge is reached.	500
facebookCookies	string	Optional encrypted cookies for content visible to your Facebook account. An authenticated session must include c_user and xs. Accepts a Cookie header, JSON browser export, or Netscape cookies.txt. Values are never written to logs or results.	—
cookieFormat	string	Automatic detection supports the common export formats. Choose a format only if detection is ambiguous. Allowed: AUTO, HEADER, JSON, NETSCAPE.	AUTO
includeRawJson	boolean	Adds rawJson as a JSON string for advanced integrations. Disabled by default because rows become much larger.	false
includePageMedia	boolean	When Facebook limits timeline pagination, fill the remaining post limit with public photo and video publications from the Page's media tabs.	true
proxyConfiguration	object	Residential proxy is recommended for reliable Facebook pagination. Cookie mode keeps one account-specific sticky proxy session; avoid changing its country between runs.	{"useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"], "apifyProxyCountry": "US"}
maxConcurrency	integer	Number of input URLs processed in parallel. Use 1–2 with Facebook cookies to reduce account warnings.	3
requestTimeoutSec	integer	Maximum time for one Facebook request.	35
maxRetries	integer	Attempts after temporary blocks or network errors. Public mode can rotate proxy sessions; cookie mode stays on its account-specific sticky session.	3
maxPaginationPages	integer	Safety limit per Page. The result limit normally stops pagination first.	50

▶️ Example input

{
  "startUrls": [
    {
      "url": "https://www.facebook.com/demo.page"
    }
  ],
  "scrapeType": "PAGES_AND_POSTS",
  "maxPostsPerPage": 20,
  "includePageMedia": true
}

📦 Output schema

Each successful item is written to the default dataset. Select a dataset view in the Apify Console or export the full dataset as JSON, CSV, Excel, XML, or RSS.

pages — 📄 Pages

Structured pages records for this Actor.

Fields: profilePictureUrl, pageName, category, followers, followings, likes, isVerified, intro, email, phone, website, coverPhotoUrl, pageUrl, pageId, scrapedAt

posts — 📝 Posts

Post-level content and engagement records.

Fields: pageName, postType, text, time, likes, comments, shares, views, mediaCount, photoUrls, videoUrls, externalLinks, postUrl, postId, scrapedAt

media — 📸 Photos & videos

Images, video, thumbnails, and storage or source URLs.

Fields: recordType, pageName, authorName, postType, profilePictureUrl, coverPhotoUrl, photoUrls, videoUrls, thumbnailUrls, mediaWidths, mediaHeights, mediaAltTexts, postUrl, pageUrl, scrapedAt

contacts — 📇 Contacts

Public contact evidence and normalized contact fields.

Fields: pageName, category, emails, phones, websites, addresses, messengerUrl, pageUrl, pageId, scrapedAt

all — 🗂️ All fields

The broadest combined dataset view.

Fields: recordType, inputUrl, sourcePageUrl, facebookUrl, pageUrl, postUrl, pageId, facebookId, postId, feedbackId, pageName, title, username, category, categories, intro, info, followers, followings, likes, comments, shares, views, isVerified, email, emails, phone, phones, website, websites, address, addresses, confirmedOwner, rating, ratingCount, messengerUrl, pageAdLibrary, profilePictureUrl, profilePictureWidth, profilePictureHeight, profilePhotoId, coverPhotoUrl, coverPhotoWidth, coverPhotoHeight, coverPhotoId, postType, authorName, authorId, authorUrl, authorProfilePictureUrl, text, caption, timestamp, time, reactionLike, reactionLove, reactionCare, reactionHaha, reactionWow, reactionSad, reactionAngry, topReactionsCount, referenceNames, referenceUrls, externalLinks, link, mediaCount, mediaIds, mediaTypes, mediaUrls, photoUrls, videoUrls, thumbnailUrls, mediaWidths, mediaHeights, mediaAltTexts, hasPhotos, hasVideo, rawJson, cookieMode, scrapedAt

📤 Example output

{
  "pageName": "Demo Studio",
  "category": "Example business",
  "followers": 12500,
  "email": "hello@example.test",
  "phone": "+1 202 XXX XXXX",
  "website": "https://example.test",
  "pageUrl": "https://www.facebook.com/demo.page",
  "pageId": "DEMO-PAGE-01"
}

Missing source values are returned as null, empty arrays, or documented availability/status fields; the Actor does not invent unavailable source data.

🔌 API example

Replace the placeholder with an Apify token and send the same input used in the Console:

curl -X POST "https://api.apify.com/v2/acts/trakk~facebook-pages-posts-scraper/runs?token=<YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"startUrls": [{"url": "https://www.facebook.com/demo.page"}], "scrapeType": "PAGES_AND_POSTS", "maxPostsPerPage": 20, "includePageMedia": true}'

For synchronous integrations, use the run-sync-get-dataset-items API endpoint. For larger jobs, start an asynchronous run and consume its default dataset when the run succeeds.

🧩 Automation and exports

• Schedule recurring runs from the Apify Console.
• Trigger downstream systems with webhooks when a run succeeds or fails.
• Reuse named monitoring keys or stores where the selected workflow supports change tracking.
• Export dataset views to JSON, CSV, Excel, XML, or RSS, or access items through the Apify API.

❓ FAQ

Do I need a login or browser session?

Use only the inputs shown in the Actor schema. If authentication or cookies are supported, the relevant encrypted field is explicitly available in the Input tab; otherwise no account is required.

Why can some fields be empty?

Source pages vary by region, content type, privacy settings, and availability. Optional enrichment also depends on the selected mode. Empty values are preserved honestly instead of being guessed.

How should I run this at scale?

Start with a small representative input, inspect the dataset and cost, then raise item limits and concurrency gradually. Use Apify Proxy when the schema exposes it, and use schedules plus monitoring keys for recurring collection.

Is the example data real?

No. Every example in this README is intentionally fictional and uses demo identifiers, reserved domains, or masked contact values.