Facebook People Search Scraper · No Cookies avatar

Facebook People Search Scraper · No Cookies

Pricing

from $5.00 / 1,000 results

Go to Apify Store
Facebook People Search Scraper · No Cookies

Facebook People Search Scraper · No Cookies

Search and find Facebook profiles by keyword without login. Get profile names, URLs, Facebook IDs, verification status, and profile pictures. Build prospect databases from Facebook people search results. No cookies, no authentication. JSON/CSV/Excel export.

Pricing

from $5.00 / 1,000 results

Rating

0.0

(0)

Developer

Data Slayer

Data Slayer

Maintained by Community

Actor stats

0

Bookmarked

68

Total users

5

Monthly active users

9 hours ago

Last modified

Share

Find public Facebook people results by keyword and export them to a clean Apify dataset—without providing Facebook login credentials or cookies. Each returned result is written to the dataset exactly as it is received, so names, profile IDs, profile URLs, visible verification signals, and picture metadata stay intact.

Watch the demo

What this Actor does

Enter a name, role, company, specialty, location phrase, or another keyword. The Actor searches public Facebook people results, removes duplicate profiles by stable public ID or URL, and saves one result per dataset item.

This Actor is for discovery. If you already know a profile URL or ID and need deeper public profile details, use the separate Facebook Public Profile Details Actor instead.

Common uses

  • Build review-ready public profile lists for recruiting or prospect research.
  • Discover specialists, creators, partners, or community members by keyword.
  • Schedule bounded recurring searches and compare exported datasets.
  • Send JSON, CSV, or Excel exports into qualification and research workflows.

Input

FieldTypeRequiredDefaultAllowedDescription
querystringYesnew york1–300 charactersName, role, company, specialty, location phrase, or keyword.
maxPagesintegerNo11–100Maximum result pages requested. The existing key and default remain compatible.
maxItemsintegerNo10001–5,000Hard maximum number of unique people rows saved.

Example:

{
"query": "software engineer new york",
"maxPages": 5,
"maxItems": 250
}

Output

Each default-dataset item is one public people result, returned unchanged. Commonly present fields include:

{
"type": "search_profile",
"profile_id": "100012345678901",
"url": "https://www.facebook.com/people/Alex-Morgan/100012345678901/",
"name": "Alex Morgan",
"is_verified": false,
"profile_picture": {
"uri": "https://images.example/profile.jpg",
"width": 120,
"height": 120,
"scale": 2
}
}

The Actor passes every field it receives through untouched: no field is renamed, added, or dropped, so existing exports and consumers keep working. Any additional keys that appear in the source result are preserved as well, and unavailable values stay null—the Actor does not infer missing attributes.

The OUTPUT key-value-store record reports:

  • status: succeeded, empty, partial, or failed;
  • page, submitted-item, saved-item, charged-item, duplicate, skipped-item, and retry counts;
  • the exact collection bound or safe functional error that stopped the run.

Run summaries are not default-dataset items and do not count as result rows.

Completion and partial coverage

Facebook search visibility varies by query, geography, public availability, and access conditions. An empty result is different from a failed request. A run is marked partial when it reaches maxPages, maxItems, the time budget, a repeated cursor, an access failure after already saving rows, or a confirmed charge limit. Check OUTPUT before treating a dataset as complete.

Privacy and data limits

  • Only public search-result fields are returned.
  • No private contact enrichment, sensitive-attribute inference, login, or cookie input is supported.
  • The Actor does not open every profile page and does not promise full profile details.
  • Removed, private, login-only, or unavailable profiles may not appear.
  • Respect applicable law, platform terms, and the rights of the people represented in your use case.

Pricing

The Actor uses pay per event: one start event plus one result event for each default-dataset person row. Empty and failed runs do not create result rows. Your Apify Console shows the exact price for your plan before you start a run.

API and automation

Run the Actor from Apify Console, Tasks, Schedules, webhooks, or the Apify API. Results are available from the default dataset in JSON, CSV, Excel, XML, and RSS formats supported by Apify.

Support

Use the Actor's Issues tab for reproducible problems. Include the run ID, input bounds, and the safe error code from OUTPUT; do not post personal data or credentials.