Catalog / Social, content & reviews
SOCIAL, CONTENT & REVIEWS
Facebook Pages
Collect public Facebook page profiles from page links or usernames: exact follower count, category, intro, website, email and phone when listed, profile and cover images, verified badge…
About this data
Collect public Facebook page profiles from page links or usernames: exact follower count, category, intro, website, email and phone when listed, profile and cover images, verified badge, and the latest post with its reaction, comment and share counts. You only pay for pages delivered.
From the actor’s Apify Store listing. The per-call endpoint may return a bounded subset; its own description is below.
Buy per call over x402
One endpoint at api.ssh.autos. Each call is one JSON POST, paid in USDC with no account or API key, and answered in the same HTTP response.
Facebook Business Pages
POST /v1/facebook/business-page
Fields include page ID/name, category, aggregate follower/following and engagement counts, description, publicly listed business phone/website, verification badge and page images where published.
One business/organization page by its Facebook username.
The source category must identify a business or organization; personal and unclassified profiles are not returned.
Posts, owner details and raw intro items are excluded.
Input
Send a JSON body to POST https://api.ssh.autos/v1/facebook/business-page.
| Field | Type | Required | Notes |
|---|---|---|---|
page | string | required | pattern ^[A-Za-z0-9][A-Za-z0-9.\-]{1,79}$ |
Returned fields
The answer is JSON: records, a list, and summary, the run status and counts. Each record has these 31 fields; a field the source does not publish comes back null.
31 fields per record
| Field | Type | Notes |
|---|---|---|
pageId | string | Facebook page id. |
profileId | string | Facebook profile id of the page. |
url | string | — |
username | string | Vanity name from the page URL, when it has one. |
name | string | — |
category | string | — |
categories | array of strings | — |
followers | integer | Exact follower count. |
likes | integer | Exact like count, for pages that still show likes. |
following | integer | — |
talkingAbout | integer | People talking about this page. |
wereHere | integer | Check-ins ("were here"). |
intro | string | The intro text shown on the page. |
email | string | — |
phone | string | — |
website | string | First website listed on the page. |
websites | array of strings | — |
address | string | — |
latitude | number | From the address map link. |
longitude | number | From the address map link. |
priceRange | string | Price range as shown, e.g. $$. |
recommendPercent | integer | Share of reviewers who recommend the page. |
reviewCount | integer | — |
services | array of strings | Services listed on the page, e.g. Dine in, Delivery. |
socialLinks | array of strings | Other accounts linked from the page, e.g. Instagram. |
verified | boolean | — |
profilePictureUrl | string | — |
coverPhotoUrl | string | — |
input | string | The page link or username as given in the input. |
scrapedAt | string | — |
error | null | Always null in the dataset. Failed pages live in OUTPUT.pageErrors and are not billed. |
Example call
npx agentcash@latest fetch https://api.ssh.autos/v1/facebook/business-page -m POST -b '{"page": "nike"}'The example values come from the API spec or the actor’s own sample input. Running it is a paid call.
What is and isn’t charged
You pay the call price for
- An answer, including a definitive “not found” or an empty result.
- Confirmed no matches returns records: [] (charged: it is an answer).
Free
- Invalid input (422), busy (503), source failure (502), timeout (504) and calls whose client hung up are never charged.
- Invalid input and source failures are not charged.
Prefer a subscription? Run it on Apify
This data source is a public actor on the Apify Store: Facebook Pages Scraper. Run it with your Apify account and plan for larger, scheduled or exported runs; it may offer more input options than the per-call endpoint.
How x402 payment works
- Your client sends the request. The API answers
402 Payment Requiredwith the price and where to pay. - The client pays from its own wallet: USDC on Base or Solana over x402, or over MPP on Tempo. No account, sign-up or API key.
- The client retries with the payment attached and gets the JSON answer in the same call. You are only charged for answers.
The AgentCash CLI in the example does all three steps for you and pays from your AgentCash wallet. Any x402 or MPP client works the same way.
Machine-readable: openapi.json · llms.txt