Facebook Page Contact Info Scraper avatar

Facebook Page Contact Info Scraper

Pricing

from $1.30 / 1,000 facebook pages

Go to Apify Store
Facebook Page Contact Info Scraper

Facebook Page Contact Info Scraper

Get the public contact details from any Facebook Page. You get the website, email, phone and street address. You also get open or closed status, linked accounts, the verified badge and follower counts. No login needed. $1.30 per 1,000 Pages, 200 per run.

Pricing

from $1.30 / 1,000 facebook pages

Rating

0.0

(0)

Developer

Dami's Studio

Dami's Studio

Maintained by Community

Actor stats

0

Bookmarked

11

Total users

8

Monthly active users

a day ago

Last modified

Share

Facebook Page Contact Info Scraper: website, email, phone and address from any public Page

Paste Pages, get one row each with the contact details the Page publishes: website, email, phone, street address, category, the social accounts it links to, and how many people follow it.

What you get is whatever that Page chose to publish. A restaurant usually fills in everything; a personal brand Page may list a website and nothing else. When a Page carries no contact facts at all, you get an uncharged row saying so rather than a row full of nulls you paid for.

InputPage links, handles or numeric Page ids
OutputOne row per Page
Ceiling200 Pages per run
Account neededNone from you
Price$1.30 per 1,000 Pages, flat on every plan

🔍 What Facebook Page Contact Info Scraper does

It reads the public About information a Page publishes and flattens it into one row. Every detail that can appear more than once comes back twice: email and emails, phone and phones, website and websites. The singular field is the first one, for a spreadsheet; the plural holds the lot, for a database. Facebook's own links are stripped out of websites, so you get the business site rather than a link back to Facebook.

Duplicates are removed before anything is read, so the same Page written as a handle in one line and a full link in another is fetched once and charged once.

socialLinks is the useful surprise on a lead list: Pages often link their Instagram, YouTube or X account in About, and each comes back as a network, a handle and a URL.

📥 What you give it

{
"startUrls": ["https://www.facebook.com/katzsdeli", "shakeshack"],
"maxPages": 50
}
FieldDefaultWhat it is
startUrlsnoneThe Pages to read. A full Page link, an About-tab link, a bare handle like katzsdeli, an @handle, a numeric Page id, or a profile.php?id= link. Up to 200 per run.
maxPagesall of themA ceiling on how many of those Pages actually get read, so you can point it at a long list and still cap the spend. 1 to 200.
proxyUrlsnoneOptional. One URL per line if you want the traffic to leave through servers you already pay for.
sessionCookiesnoneOptional, and most runs never touch it. Your own c_user and xs pair, so heavy runs use your account's own rate limit. Treat the values like a password.

Run it with empty input and you get one labelled sample row, free, so you can see the shape before you spend anything.

📤 What you get back

A real row from a real run:

{
"ok": true,
"charged": true,
"recordType": "page",
"inputUrl": "https://www.facebook.com/katzsdeli",
"handle": "katzsdeli",
"pageName": "Katz's Delicatessen",
"pageUrl": "https://www.facebook.com/katzsdeli/",
"pageId": "100064806517961",
"isVerified": false,
"category": "Deli",
"categories": ["Deli"],
"website": "http://katzsdelicatessen.com/",
"websites": ["http://katzsdelicatessen.com/"],
"email": "cs@katzsdelicatessen.com",
"emails": ["cs@katzsdelicatessen.com"],
"phone": "(212) 254-2246",
"phones": ["(212) 254-2246"],
"address": "205 E Houston St, New York, NY, United States, 10002",
"socialLinks": [
{ "network": "Instagram", "handle": "katzsdeli", "url": "https://www.instagram.com/katzsdeli" }
],
"openingHoursStatus": "Open now",
"priceRange": "Price Range · $$",
"services": "Dine-in · Outdoor seating · In-store pickup",
"ratingSummary": "98% recommend (52,515 reviews)",
"recommendPercent": 98,
"reviewsCount": 52515,
"followers": "936K followers",
"followersApprox": 936000,
"likesCount": null,
"talkingAboutCount": 66154,
"checkinsCount": 529265,
"profilePicture": "https://lookaside.fbsbx.com/lookaside/crawler/media/?media_id=100064806517961",
"bio": "New York City's most iconic deli.",
"scrapedAt": "2026-09-21T01:31:06.640Z"
}
FieldWhat it is
inputUrl, handle, pageId, pageUrlWhat you asked for, and the three ways to identify the Page afterwards. pageId is the key that never changes.
email / emails, phone / phones, website / websitesFirst value and full list. Phones come back in the format the Page published them in, so a French Page gives a French format.
addressOne line, as published. There are no separate street, city and postcode fields, because the Page does not publish them separately.
category, categories, bio, services, priceRangeHow the Page describes itself and what it says it offers.
socialLinksOther accounts linked from About, each with network, handle and url.
openingHoursStatusThe live status line only, such as Open now or Closed now.
ratingSummary, recommendPercent, reviewsCountThe recommendation line on Pages that have one, split into a number and a count.
followers, followersApprox, likesCountFacebook publishes followers as a rounded string ("936K followers"). followersApprox is that string as a number, so it is rounded too.
talkingAboutCount, checkinsCountExact figures, not rounded, on Pages that publish them.
isVerified, profilePicture, scrapedAtThe blue badge, the Page picture, and when the row was read.

Anything the Page does not publish comes back null or empty rather than guessed.

🧾 Reading the output

Three kinds of row can land in your dataset.

RowHow to spot itBilled
A Pageok: true and charged: trueyes
The sample row_sample: trueno
A diagnostic_diagnostic: true and an errorCodeno

Filter on charged == true and you have your data. That flag is what separates real rows from the sample and the diagnostics, not a receipt.

errorCodeWhat happened
BAD_INPUTThat entry could not be read as a Page.
NOT_FOUNDNo public Page there. Misspelled handles and deleted Pages land here.
NO_CONTACT_INFOThe Page is readable but publishes no contact details at all.
BLOCKEDFacebook would not serve that Page on this run. Re-running usually clears it.
NETWORKFacebook could not be reached.
TIME_BUDGETThe run ran out of time before reaching that Page.
PROXY_INPUT_ADJUSTEDA proxyConfiguration setting this Actor does not use was dropped. The run carried on.
CHARGE_ERRORA billing event could not be recorded. Told to you rather than hidden.
UNEXPECTED_ERRORAnything else, with the message attached.

If a run refuses from the start and nothing at all has been delivered, it stops instead of grinding through the rest of your list. The Pages it did not reach are named in a single uncharged BLOCKED row, so you know exactly what to re-run.

One quirk of the Console's Overview table: it shows the identity and contact columns, so the address, the social links, the opening status and the audience counts read as missing there. Open the row or download the JSON and they are all present.

▶️ How to run it

  1. Open Facebook Page Contact Info Scraper and click Try for free.
  2. Put your Pages into Facebook Pages, one per line.
  3. Set Maximum Pages to read if you are pointing it at a long list and want a spend ceiling.
  4. Click Start.
  5. Download the dataset as JSON, CSV or Excel, or pull it from the Apify API.

💰 How much does it cost?

$1.30 per 1,000 Pages. The same rate on every Apify plan, no volume tiers.

You pay for Pages that come back with contact details. The sample row, every diagnostic row, duplicate spellings of the same Page, Pages that publish nothing to find and Pages the run never reached are not charged.

💡 What people use it for

  • Turning a list of Page handles into a call sheet with email, phone and website on one line.
  • Enriching a CRM: match on pageId, fill the blanks, and use socialLinks to find the accounts nobody recorded.
  • Local research, where address, category and priceRange give you the shape of a high street in one run.
  • Checking whether Pages you already work with still publish the contact details you have on file.

🚧 What it does not do

  • Only what the Page publishes. No email is inferred, guessed or looked up elsewhere. A Page with a blank About section returns an uncharged row saying so.
  • No weekly opening timetable. You get the live status line, Open now or Closed now, not Monday to Sunday hours.
  • Follower counts are rounded, because Facebook rounds them before publishing. talkingAboutCount and checkinsCount are exact where they exist.
  • No posts, reviews or comments. Those are separate Actors, linked below.
  • Public Pages only. Personal profiles, groups and anything behind a login are out of scope.
  • Phone and address arrive region-formatted, as the Page wrote them, not normalised to one standard. Parse them if you need parts.
  • 200 Pages per run. Split a bigger list across runs.

🧭 Which Facebook scraper do you need?

If you wantUse
The contact details on a PageThis one
What that Page has been postingFacebook Posts Scraper
The recommendations and reviews under itFacebook Reviews Scraper
Reels from that PageFacebook Reels Scraper
The comments under one of its postsFacebook Comments Scraper

❓ Questions people ask

Do I need a Facebook account? No. Public Pages read fine without one. sessionCookies is there for people running heavily who would rather use their own account's rate limit.

Can I give it a numeric Page id? Yes, and an @handle, a bare handle, an About-tab link or a profile.php?id= link. They all resolve to the same Page.

Why is the email missing on some Pages? Because the Page did not publish one. Nothing here guesses an address from a domain.

What happens if I paste the same Page twice? It is read once and charged once. Duplicates are removed before anything is fetched.

Is scraping Facebook legal? This reads public Page information only. Business contact details are still personal data under GDPR and similar laws, so have a reason for collecting them and respect opt-outs. Apify's write-up on the legality of web scraping is a good starting point, and we are not lawyers.

Can I run it on a schedule? Yes, on Apify's scheduler, or start it from the API and read the dataset when it finishes.

🆘 If something breaks

Open the Issues tab on the actor page. Paste the Page you used and the run ID, and the log is enough for us to see what happened.