# Facebook Posts Scraper (`cleansyntax/facebook-posts-scraper`) Actor

Scrape Facebook Posts with one tool - pay-as-you-go, no monthly subscription. Collect profile posts, get profile details by page URL or ID, or get a profile ID from a URL.

- **URL**: https://apify.com/cleansyntax/facebook-posts-scraper.md
- **Developed by:** [CleanSyntax](https://apify.com/cleansyntax) (community)
- **Categories:** Social media, Automation, Developer tools
- **Features:** Limited permissions
- **Stats:** 615 total users, 29 monthly users, 99.9% runs succeeded, 2 bookmarks
- **User rating**: 5.00 out of 5 stars

## Pricing

$6.00 / 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.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

**📘 Facebook Posts Scraper**

Scrape Facebook Posts — recent **profile posts**, **profile details** (by ID or URL), and **profile ID lookup** — powered by our **Facebook Scraper**.

***

### ✨ Features

- **Profile posts**: Fetch public profile posts **by ID** or **by URL**.
- **Profile details**: Retrieve rich profile metadata **by ID** or **by URL**.
- **Profile ID lookup**: Resolve a profile **ID** from a URL

### 🧭 Endpoints

Choose one endpoint per run:

1. **`profile_posts_by_url`**
   `GET /profile/posts?profile_url=...&start_date=YYYY-MM-DD&end_date=YYYY-MM-DD`

2. **`profile_posts_by_id`**
   `GET /profile/posts?profile_id=...&start_date=YYYY-MM-DD&end_date=YYYY-MM-DD`

3. **`details_by_id`**
   `GET /profile/details_id?profile_id=...`

4. **`details_by_url`**
   `GET /profile/details_url?url=...`

5. **`profile_id_by_url`**
   `GET /profile/profile_id?url=...`

***

### 🚀 How It Works

1. Pick the **endpoint** in the Actor input (dropdown).
2. Fill only the parameter(s) required for that endpoint.
3. Run the Actor.

   - For **Profile posts**, the Actor:

     - Calls `GET /profile/posts?profile_url/id=...` (+ optional `start_date`, `end_date`),
     - Pushes posts to the dataset,
     - Continues with `GET /profile/posts?profile_url/id=...` until finished.

All results are stored in the **default Apify Dataset**, ready to export as **CSV**, **XLSX**, or **JSON**.

***

### 🧾 Input

#### Fields

- **`endpoint`** *(required)* — one of:

  - `profile_posts_by_id`
  - `profile_posts_by_url`
  - `details_by_id`
  - `details_by_url`
  - `profile_id_by_url`
- **`profile_id`** *(string)* — required for `profile_posts`, `details_by_id`
- **`profile_url`** *(string)* — required for `profile_posts`, `details_by_url`
- **`url`** *(string)* — required for `details_by_url`, `profile_id_by_url`
- **`start_date`** *(YYYY-MM-DD, optional)* — filter for `profile_posts`
- **`end_date`** *(YYYY-MM-DD, optional)* — filter for `profile_posts`

### 📦 Output

All results are saved as items in the **default Apify Dataset**.

#### Profile posts

Each dataset item is a **post** object from the API, plus helper fields:

- `profile_url or profile_id (search term)` — the URL or ID you queried

Common fields (may vary):
`post_id`, `type`, `url`, `message`, `timestamp`, `comments_count`, `reactions_count`, `reshare_count`, `reactions` (object), `author` (object), media (`image`, `video`, `video_files`, `video_thumbnail`, `album_preview`, `external_url`).

#### Profile details (by ID / by URL)

Single record with profile metadata (structure depends on API). We push `results` if present, otherwise the raw payload, plus:

- `profile_id (search term)` **or** `url (search term)`

#### Profile ID by URL

Single record containing the resolved **profile ID**, plus:

- `url (search term)`

> Export via **Dataset → Export** in the Apify UI (CSV, XLSX, JSON).

### 🧠 Reliability & Pagination

- **Pagination**: Automatically keeps requesting until the API stops returning profile posts.
- **Retries**: 3 attempts with a 5s backoff for transient failures (e.g., 429/5xx).
- **Polite delay**: A short delay between requests helps reduce rate-limit hits.
- **Minimal logs**: Progress lines look like:

  ```
  total posts collected 3
  total posts collected 6
  ```

***

### 🛡️ Best Practices

- Use realistic workloads; although the Actor retries on 429/503, excessive calling can still be throttled.
- For very large profiles, consider narrowing **date filters** or splitting runs.
- Profiles must be **public** for data to be returned by the API.

***

### 🔧 Troubleshooting

- **422 `Field required: profile_id`**
  The API requires `profile_id` even when using a `cursor`. This Actor always includes it; ensure your input has `profile_id` filled.

- **429 Rate limited**
  The Actor retries up to 3 times with a 5s delay. If it persists, slow down or split the job.

- **No posts returned**
  The profile may be private, there may be no posts, or your date range excludes available posts.

- **Empty details/ID**
  Double-check the URL/ID. Some profiles or URLs may not resolve or be supported.

### 📈 SEO Keywords

facebook post scraper, scrape facebook posts, facebook profile details api, facebook profile id lookup, apify actor facebook, facebook cursor pagination, export facebook posts csv, facebook profile details by url, facebook profile details by id, automate facebook scraping

# Actor input Schema

## `endpoint` (type: `string`):

Choose what to fetch.

## `urls_text` (type: `string`):

Use for: Profile posts by URL, Profile details by URL, Profile ID by URL. Paste one URL/username per line.

## `ids_text` (type: `string`):

Use for: Profile posts by ID, Profile details by ID. Paste one profile_id per line.

## `keywords_text` (type: `string`):

Use for: Search Posts by Keyword. Paste one search query per line.

## `max_posts` (type: `integer`):

Optional. Limit how many posts to collect per profile or keyword. Set 0 (default) to fetch all available.

## `start_date` (type: `string`):

Optional filter for Profile posts and Search posts.

## `end_date` (type: `string`):

Optional filter for Profile posts and Search posts.

## Actor input object example

```json
{
  "endpoint": "details_by_url",
  "urls_text": "https://www.facebook.com/lodibeercompany/",
  "max_posts": 0
}
```

# 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 = {
    "endpoint": "details_by_url",
    "urls_text": "https://www.facebook.com/lodibeercompany/",
    "max_posts": 0
};

// Run the Actor and wait for it to finish
const run = await client.actor("cleansyntax/facebook-posts-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 = {
    "endpoint": "details_by_url",
    "urls_text": "https://www.facebook.com/lodibeercompany/",
    "max_posts": 0,
}

# Run the Actor and wait for it to finish
run = client.actor("cleansyntax/facebook-posts-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 '{
  "endpoint": "details_by_url",
  "urls_text": "https://www.facebook.com/lodibeercompany/",
  "max_posts": 0
}' |
apify call cleansyntax/facebook-posts-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,cleansyntax/facebook-posts-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/5WFSjgBncmr2hnRGl/builds/wt1DlaSLNM0wsUqYv/openapi.json