Facebook hub

Facebook Profile API

Resolve a public Facebook page or profile URL to structured JSON — display name, avatar, likes and followers, contact and business fields — without a Meta Graph app for assets you do not own.

GET /v1/facebook/profiles

1 credit per successful request.

About this endpoint

Brand trackers, local SEO tools, and competitive research jobs usually start with a Facebook URL, not a numeric page id. You need to know whether the URL is a person or a business page, pull likes and followers when Facebook shows them, and store contact lines or category text for enrichment. Homegrown Facebook page scrapers stall on login walls and markup that shifts every few months.

`GET /v1/facebook/profiles` takes a public Facebook profile or page `url` query param and returns the shared Social Fetch envelope. Branch on `data.lookupStatus` before you write a row — `found`, `private`, and `not_found` are explicit outcomes. On `found`, read `data.profile` (including `profileType` of `person` or `business`), plus `metrics`, `contact`, and `business` when present. Pass `includeBusinessHours=true` when you need structured opening hours for a page that publishes them.

This route returns the page or profile card only. Posts, reels, and photos are separate paths on the Facebook hub. Pricing is on the credit badge for this operation; bill from `meta.creditsCharged` on every response.

Facebook Profile API FAQ

How do I look up a Facebook page or profile via API?

Call `GET /v1/facebook/profiles` with your Social Fetch API key (`x-api-key`) and a public Facebook `url` query param. Read `data.lookupStatus` and the profile payload in the JSON response. Full parameters and examples are in the API docs.

How much does the Facebook Profile API cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged — that field is the billing source of truth.

What fields does the Facebook profile response include?

When `lookupStatus` is `found`, the payload can include profile identity (`profileType`, display name, profile URL, avatar, cover, platform user id), metrics such as likes, followers, and rating count, public contact fields (address, email, phone, website), and business-page fields such as category, intro, services, price range, and optional structured hours when you request them.

Does this work for both personal profiles and business Pages?

Yes. The same route accepts public profile and Page URLs. Check `data.profile.profileType` — `person` or `business` — and treat `business` fields as optional. Coverage follows what Facebook shows publicly on that URL.

Do I need Meta Graph API access or page admin rights?

No. Social Fetch returns publicly visible page and profile data for enrichment-style lookups. Meta's Graph and Marketing APIs are for assets and ads accounts you control or that authorize your app — not arbitrary public competitor pages.

What happens for private or missing Facebook profiles?

The call still returns a typed `lookupStatus`. Private targets resolve as `private`; unknown or removed URLs as `not_found`. Do not invent likes, bios, or contact lines. Keep `meta.requestId` if you need support on a failed enrichment row.

Facebook profile lookup vs posts or reels endpoints?

Use `GET /v1/facebook/profiles` for the page or profile card. For content lists use `GET /v1/facebook/profiles/posts`, `GET /v1/facebook/profiles/reels`, or `GET /v1/facebook/profiles/photos`. See the Facebook platform hub for the full list.