Facebook Accounts Scraper — Pages, Profiles & Groups avatar

Facebook Accounts Scraper — Pages, Profiles & Groups

Pricing

from $2.10 / 1,000 account with verified data

Go to Apify Store
Facebook Accounts Scraper — Pages, Profiles & Groups

Facebook Accounts Scraper — Pages, Profiles & Groups

Scrape Facebook Pages, profiles and groups for contact details, audience, About information and Page transparency when publicly available.

Pricing

from $2.10 / 1,000 account with verified data

Rating

5.0

(2)

Developer

Data Wan

Data Wan

Maintained by Community

Actor stats

2

Bookmarked

3

Total users

2

Monthly active users

a day ago

Last modified

Categories

Features

Limited permissions

Share

Facebook Accounts Scraper — Pages, Profiles & Groups

Enrich a list of public Facebook accounts with identity, audience counts, contact details and available About information. This Facebook scraper supports Pages, profiles and public groups in one batch, returning structured records for research, account matching and ongoing monitoring. No Facebook login or supplied cookies are needed.

Why choose this Facebook scraper?

  • One batch for mixed account lists. Submit up to 1,000 Page, profile and public-group references together. Automatic enrichment means no collection modes to choose.
  • Context beyond names and follower counts. Build richer account records with available public About and transparency details, including gender, creation dates and management countries where exposed. Availability depends on the account and source response.
  • Useful results even with gaps. Verified fields survive an unavailable section, so you can use partial records while checking exactly which sections have issues.
  • Results you can join back to your list. Ordered rows preserve every input occurrence, including duplicates, with an input index and status for matching results to CRM records.
  • Precision you can assess. Counts and dates retain source and accuracy or precision; unknown values stay distinct from zero, helping you avoid treating estimates as exact facts.

Pay only for newly collected results with verified account data. Empty results and reused observations are free. Partial results are billed too, including an identity-only result with a verified account ID.

Pricing

Pay per newly collected result with verified data. Rates per 1,000 results are:

Apify plan tierPrice per 1,000
FREE$3.00
BRONZE$2.70
SILVER$2.40
GOLD, PLATINUM, DIAMOND$2.10

There is no minimum charge. Platform usage is included in the event price; this Actor does not add a separate platform-usage charge. Use the latest build for discounted rates; older pinned builds may reject discounted runs before collection.

A saved collected or partial row with a verified id is billable when it comes from a new collection. unsupported, unavailable, notProcessed and rows without a verified ID are free. A duplicate is free when its row says reused: true; references that cannot yet be proved to identify the same account may require separate collections and charges. A fresh run is a new observation and may charge again.

Set Apify's maximum total charge before starting. Collection reserves the remaining result allowance; an earlier free result releases its reservation for the next account. When another result is no longer affordable, the Actor stops new collection. Cached observations and unsupported inputs can still be returned; other inputs receive notProcessed with budgetReached. Consult remainingInputs before starting another run.

Quick start

  1. Open this Actor in Apify Console and go to Input.

  2. In the JSON editor, paste this example:

    {"targets": ["https://www.facebook.com/facebook"]}
  3. Click Start, then inspect the results in Output. Check each row's status before using its data.

  4. Click Export to download the dataset. JSON preserves the nested account details; CSV and Excel are also available.

To try a Page, profile and group together, use:

{
"targets": [
"https://www.facebook.com/facebook",
"https://www.facebook.com/zuck",
"https://www.facebook.com/groups/874728723021553"
]
}

These are example targets, not a promise that every field will be available when you run them. Enrichment is automatic: the Actor attempts the supported public sections it can access. There are no basic/full modes, field-selection switches or proxy settings to configure.

Supported inputs

targets is the only input field. Supply 1–1,000 strings, each at most 2,048 characters. You can mix:

  • Facebook desktop/mobile account URLs, usernames or @username references.
  • Numeric IDs, profile.php?id=<numeric-id> and /people/name/<numeric-id>/ URLs.
  • Legacy /pages/name/<numeric-id>/ URLs and group URLs. A bare numeric group ID works when Facebook supplies a matching group route.
  • Root pfbid… and /people/name/pfbid…/ references. Preserve their exact case; these opaque references have limited enrichment, explained below.

Post, reel, event and search URLs are unsupported. This Actor enriches accounts you supply; it does not search for accounts or collect posts and comments.

What data can I get?

Availability varies by account and by what Facebook exposes anonymously. Fields below are possible outputs, not a completeness guarantee.

Account typeAvailable public information
PagesIdentity, name, URL, images, bio/description, categories, websites, email/phone, address, business hours, services, price/rating text, audience counts, creation dates and transparency information, including management countries and advertising observations
ProfilesIdentity, name, URL, images, bio/description, audience counts, public contact details, raw public gender value, work, education, places, relationship, Life Events references and available creation/transparency observations
Public groupsIdentity, name, URL, cover image, description, member count, creation date, privacy/discoverability, rules, topics, locations and aggregate activity

Public gender is copied as Facebook reports it, including values such as UNKNOWN; it is never inferred from a name or image. About gender/pronouns can appear separately as labeled observations. Creation dates retain their source and precision; conflicting observations remain visible. Management countries describe where an account is managed, not the owner's home or business address. Unknown and opted-out manager counts stay separate.

No private content, member/admin/follower lists or media files are collected. Image and photo-page URLs are references and may expire or change. Life Events references are not followed to collect their posts.

Reading your results

The dataset contains one row per input occurrence, in input order when normal storage completes. Up to four observations can be collected at once; rows are still saved in input order. Repeated inputs share their observation, including its timestamp and partial/unavailable outcome. Different references can require separate collection until their returned identity proves they name the same account. Later proved reuse takes the earlier observation for free; reused identifies those rows. Start a new run when you need a fresh observation.

inputIndex is the zero-based input position. input is a safe normalized reference; rejected strings become unsupported-input. Resolved identity and canonical URL can differ from the supplied reference. id preserves the observed Header object ID, which can be numeric or opaque. facebookId is the numeric account identity corroborated by this source observation, or null when that evidence is missing. It describes the resolved account, even when the input named its linked Page. linkedPageId remains that separate Page's identity; routeUserId remains an observation-specific request selector. These fields do not promise permanent URLs or opaque-token lifetimes, and facebookId does not create additional input aliases or change reuse within a run.

Row statusMeaning and next step
collectedIdentity verified and supported sections inspected. Use the returned fields; some can still be unknown.
partialUseful verified data retained with gaps. Inspect issues and sections before using it.
unavailableNo verified account data from this attempt. Check the reference and reported reason.
unsupportedUnsupported or unsafe reference; no request made for it. Correct the input format.
notProcessedSource work stopped before this occurrence, for example after a block, deadline or charge limit. Review the run summary for unfinished inputs.

Null is unknown, not zero. An explicit zero or returned empty list is distinct from missing data. Counts retain display, accuracy and source: a rounded 1.2K followers label does not become an invented exact integer. exact means an unabridged source-reported count, not an independently measured audience. The same distinction applies to group members.

This synthetic excerpt illustrates a useful partial result. It is not a live sample; full rows include additional metadata and run fields, with nulls for unknown values.

{
"inputIndex": 0,
"input": "https://www.facebook.com/examplegarden/",
"id": "123456789",
"facebookId": "123456789",
"name": "Example Garden",
"accountType": "page",
"followers": {
"value": null,
"display": "1.2K followers",
"accuracy": "approximate",
"source": "header.followers"
},
"creationDates": [
{
"value": "2020-01-01T12:00:00Z",
"precision": "second",
"source": "transparency.history.CREATION"
}
],
"transparency": {
"managerCountries": [{"country": "Canada", "count": 2}],
"unknownManagerCount": 0,
"optedOutManagerCount": 0
},
"status": "partial",
"sections": ["header", "about", "transparency"],
"issues": [{"section": "about_details", "reason": "missingSection"}]
}

Limits and recovery

The first source block or rate limit stops new Facebook requests for the whole run. Requests already in flight may finish, and verified fields already acquired are retained. Up to four in-flight results can therefore be saved as billable partial rows, including identity-only results with a verified account ID. An input that sent a source request but stopped before verified data is free unavailable with blocked. Inputs blocked before their first request, without verified identity, and unstarted inputs receive free notProcessed with blocked. An unavailable result does not prove an account is private, deleted or nonexistent. Group privacy must be confirmed public before deeper enrichment.

Each input initially has a 120-second enrichment budget. Under the default 24-hour platform limit, aggregate source work stops after 23 hours to leave time for saving remaining rows and cleanup. Shorter platform deadlines reduce source time. Large or slow batches may not inspect all inputs; hard timeouts and user aborts can interrupt saving too.

The key-value record OUTPUT summarizes accepted inputs, acknowledged rows, rows with data, outcomes and remainingInputs (indices into your original input). This retry list contains unacknowledged or notProcessed occurrences, including zero-request blocked inputs. An acknowledged unavailable row with an actual attempted request and blocked is excluded. Inspect row outcomes too before deciding what to resubmit. Detailed metadata lives in dataset rows. The stored summary can lag the dataset during execution or after a hard kill. An uncertain append is not retried, so a row may exist without acknowledgment. Billing follows acknowledged row storage. If a charge fails or its response is uncertain, the run fails technically and keeps already saved data; a charge may still have reached the platform. The last affordable charge waits until the remaining free rows and a full running summary are saved. A platform stop at that boundary can leave the summary marked running even though all rows were saved. A hard stop before settlement can leave a saved result uncharged. Use the dataset and Apify's charge history together; the summary is not a billing receipt. Inspect and deduplicate existing results before submitting unfinished inputs in a fresh run. There is no in-run resume; existing execution storage is refused.

FAQ

Why is a public account partial or unavailable?

Anonymous access and fields vary. Read issues for the affected section and reason. protocolError means the response could not be interpreted; foreignIdentity means its identity could not be verified. Neither proves the account is missing. Opaque pfbid… routes currently retain verified identity and available images only, with partial coverage; About enrichment across their different identity forms is not verified.

Do I need a Facebook account, cookies or a proxy?

No login or imported cookies are accepted. Facebook-issued anonymous cookies stay in memory. Proxy use for eligible count requests is managed by the Actor; there is no input setting.

Why did the run succeed if some rows have no data?

Run success means processing and required storage completed, not that every account was available. Invalid input envelopes reaching the Actor return OUTPUT.status=invalidInput with no rows; Apify can reject them before a run starts. Configuration, programming, storage and cleanup errors fail the run technically.

How can I automate repeat collection?

Use Apify's API to start runs and retrieve datasets, or schedule recurring runs. See Run Actors and Schedules (official guides checked November 8, 2026). Keep each run's observation time when comparing results: availability and account metadata can change.

How do I report a problem?

Open an issue in this Actor's Issues tab with the run ID, row status/reason and the field you expected. Include a public example reference only if appropriate to share. Do not include credentials, cookies, access tokens or private data.