Facebook Page Posts Monitor - Public Posts & Engagement API

Monitor public Facebook pages for visible post and page signals. Export page names, post URLs, text snippets, images, external links, timestamps when available, and engagement counters when Facebook exposes them.

Use cases

• Track competitor Facebook page activity
• Monitor brand pages and local business pages
• Build social listening alerts for public posts
• Export Facebook page metadata for lead lists
• Schedule recurring page monitoring via Apify API

What you get

• Page name, page ID when available, and canonical page URL
• Visible public post URLs and post IDs
• Post text/snippet from public embedded data
• Image/video URLs when exposed
• External links mentioned near the post
• Reaction, comment, and share counters when exposed
• Diagnostics for restricted/login/checkpoint pages

Important notes

Facebook frequently changes logged-out access. This Actor is designed to be transparent: if Facebook serves a restricted page, the run summary explains it. For better coverage, provide your own Facebook Cookie header and use Apify Proxy. Only scrape public content and accounts you are allowed to access.

Input example

{
  "pageUrls": [
    "https://www.facebook.com/humansofnewyork",
    "nike"
  ],
  "maxPostsPerPage": 25,
  "dedupe": true,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}

Output fields

{
  "pageName": "Humans of New York",
  "postId": "1234567890",
  "postUrl": "https://www.facebook.com/example/posts/1234567890",
  "text": "Visible public post text...",
  "publishedAt": "2026-06-19T12:00:00.000Z",
  "reactionsCount": 120,
  "commentsCount": 12,
  "sharesCount": 5,
  "imageUrl": "https://...",
  "externalLinks": ["https://example.com"],
  "extractionMethod": "embedded_json"
}

Recommended saved tasks

• Competitor Facebook page monitor
• Brand Facebook page alerts
• Local business page tracker
• Publisher/social newsroom monitor
• Creator page activity monitor

Input reference

Field	Description
pageUrls	Public Facebook Page URLs or handles
pageUrlsText	Bulk newline-separated Page inputs
maxPostsPerPage	Maximum visible post rows retained per Page
includePageMetadata	Return a Page metadata fallback when posts are unavailable
cookie	Optional user-provided Cookie header for permitted access
dedupe	Remove duplicate post URLs
proxyConfiguration	Apify or custom proxy settings

API example

curl -X POST \
  "https://api.apify.com/v2/acts/groupoject~facebook-page-posts-monitor/runs?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "pageUrls":["https://www.facebook.com/humansofnewyork"],
    "maxPostsPerPage":25,
    "includePageMetadata":true
  }'

Monitoring workflow

1. Add public Page URLs or handles.
2. Run a small test and review extractionMethod and diagnostics.
3. Save the configuration as a task.
4. Schedule the task at a reasonable interval.
5. Deliver results to a webhook, database, spreadsheet, or social-listening dashboard.

Reliability and access

Facebook serves different logged-out responses by Page, region, and session. The Actor records transparent diagnostics instead of fabricating missing post data. A Page metadata fallback can keep monitoring workflows observable when post rows are not publicly exposed.

FAQ

Does it require Facebook login?

It first attempts public access. For pages that require logged-in access, you may provide your own Cookie header only when you are authorized to access and process that content.

Does it scrape private groups or profiles?

No. It is designed for publicly accessible Facebook Pages and visible public signals.

Why are engagement fields null?

Facebook does not expose every counter in every public response. Missing values remain null.

Can I monitor several Pages?

Yes. Add multiple Page URLs or use the bulk input, then control run size with maxPostsPerPage.

Comply with Facebook's terms, privacy rules, and applicable laws. Do not use the Actor to bypass access controls.

Pricing and billing

Base result price checked September 14, 2026: $3.00 per 1,000 dataset items ($0.003 each). 100 result items cost $0.30 in result fees.

The separate Actor start event is $0.00005 per billable start unit, with one unit per GB of configured memory and a minimum of one. It applies even when a run returns no results.

A result event corresponds to one item saved in the default dataset, not one HTTP request or one input URL.

The live Pricing tab is authoritative for current rates, tier discounts and any separately charged usage. Set a maximum run charge and inspect a small sample before scaling. Charges from an external provider, where used, are not controlled by the Apify run-charge limit.