# Facebook Page Scraper (`thenetaji/facebook-page-scraper`) Actor

Collect a public Facebook Page's details: its ID, category, contact information, website and social links, and Page Transparency information such as creation date, ad status and confirmed owner. No Facebook login is used.

- **URL**: https://apify.com/thenetaji/facebook-page-scraper.md
- **Developed by:** [The Netaji](https://apify.com/thenetaji) (community)
- **Categories:** Social media, Marketing
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.40 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Facebook Page Scraper — Profile & About

The Actor reads a public Facebook Page's profile exactly as a logged-out visitor sees it: its numeric ID, permalink, and — where requested — its About section and Page Transparency details. No Facebook account, login, or session cookie is used at any point, and nothing is collected beyond what an anonymous visitor to the Page can already see.

### Accepted input

`page` is required and accepts a list in which each entry is a Page's username (the part after `facebook.com/`), its numeric ID, or a full `facebook.com/<page>/` URL; the three forms can be mixed in one run. A URL is reduced to the identifier before the request is made, and a leading `@` is stripped, so `@nasa`, `nasa`, and `https://www.facebook.com/nasa/` all resolve to the same Page. Duplicate entries are collapsed before any request is issued.

```json
{
  "page": ["NASA", "https://www.facebook.com/unicef/"],
  "includeAbout": true,
  "includeTransparency": false
}
```

### Result fields

Each row carries `page`, `pageId`, `url`, `about`, `transparency`, and `raw`. `raw` carries the complete profile record Facebook returned, beyond what is broken out into its own field.

`includeAbout` (default `true`) adds the Page's About section — category, contact details, website and social links, and business information where the Page is a business — under `about`. `includeTransparency` (default `false`) adds Page Transparency details — creation date, admin country information, ad status, and confirmed owner — under `transparency`. Both are opt-in and each is fetched as its own request, so a run that only wants a Page's ID and URL is not charged for either.

The example below illustrates field shapes; it is not captured from a live run.

```json
{
  "page": "NASA",
  "pageId": "23497828950",
  "url": "https://www.facebook.com/NASA/",
  "about": { "category": "Government organisation", "profile_email": "public-inquiries@hq.nasa.gov", "website": ["http://www.nasa.gov/", "https://www.nasa.gov/nasa-app/"] },
  "transparency": null
}
```

`about` and `transparency` are flat maps of field name to text, keyed by Facebook's own field names rather than reshaped into a fixed set of columns; the fields a Page carries vary by Page type. Both are `null` when their toggle is off, and can also be `null` when the toggle is on but Facebook's own document did not carry that section for the Page.

### Behaviour on partial results

Each Page is read with a single request. A Page that cannot be resolved — because the username or ID does not exist, or the Page is not public — is logged as a warning and skipped, and the run continues with the rest of the list. A run of ten Pages in which one is unreachable finishes with records for the other nine.

### Public, logged-out data only

Every field returned here comes from what Facebook serves to an anonymous visitor. The Actor does not sign in, does not use a Facebook account or cookie of any kind, and cannot read anything a logged-out visit to the Page would not already show. A Page that requires a login to view returns no record.

### Frequently asked questions

**What happens for a Page that does not exist or is not public?**
No record is saved for it. The run log names the Page and the run continues with the rest of the input.

**Is `about` or `transparency` guaranteed to be populated when requested?**
No. Both return `null` when the toggle is on but Facebook's own document did not carry that section for the Page — a personal-style Page with no business information filled in, for example.

**Does this Actor also return the Page's posts?**
No. Profile fields only. Use the [Facebook Posts Scraper](https://apify.com/thenetaji/facebook-posts-scraper) for timeline posts from the same Page.

### What this is useful for

Tracking a competitor's or partner's Page details over time; pulling public contact and social-link information from a Page's About section for outreach and lead research; and checking a Page's Transparency information — creation date, ad status, confirmed owner — as part of verification work.

### Related Actors

| Actor | Purpose |
| --- | --- |
| [Facebook Posts Scraper](https://apify.com/thenetaji/facebook-posts-scraper) | Timeline posts for a Page |
| [Facebook Followers/Following Scraper](https://apify.com/thenetaji/facebook-followers-following-scraper) | Followers and following lists for a Page |
| [Facebook Marketplace Scraper](https://apify.com/thenetaji/facebook-marketplace-scraper) | Marketplace listings by category |

# Actor input Schema

## `page` (type: `array`):

Facebook Page usernames, numeric IDs, or full facebook.com/<page>/ URLs, one per line.

## `includeAbout` (type: `boolean`):

Adds the Page's About section — category, contact details, website and social links, and business information where the Page is a business.

## `includeTransparency` (type: `boolean`):

Adds Page Transparency details — creation date, admin country information, ad status and confirmed owner.

## Actor input object example

```json
{
  "page": [
    "NASA",
    "https://www.facebook.com/unicef/"
  ],
  "includeAbout": true,
  "includeTransparency": false
}
```

# Actor output Schema

## `dataset` (type: `string`):

All records scraped by this run

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "page": [
        "NASA"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("thenetaji/facebook-page-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "page": ["NASA"] }

# Run the Actor and wait for it to finish
run = client.actor("thenetaji/facebook-page-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "page": [
    "NASA"
  ]
}' |
apify call thenetaji/facebook-page-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,thenetaji/facebook-page-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/Yk4qIAI4WrCaorCRe/builds/hDZcAvyL6Bh7NlJTm/openapi.json