Get Facebook page details API

Endpoint facts

Method

GET

API path

/facebook/{page}

Auth

apiKey

Credits

10 credits/request

Platform

Facebook

Response schema

#/definitions/facebook.pageResponseDoc

Overview

Fetches public data about a Facebook Page given its page ID, vanity name, or full page URL: name, follower/like counts, intro, category, business hours/price range, review count, and any public contact details (email, phone, address, website, WhatsApp number) exposed on the Page's About tab. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

10 credits/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

• Proxy strategy: managed automatically where needed
• Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
• Browser cluster: supported dynamic workloads can be routed through distributed browser instances
• Retry behavior: automatic retry/fallback may be used depending on endpoint type
• Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Response behavior

`category`, `hours`, `priceRange`, `whatsapp`) are populated when the Page publishes them on its About tab; they are omitted when a Page doesn't expose them. `emails`/`phones` are extracted independently and may contain more than one value; `email` is the first extracted address, kept for backward compatibility. `pageId` is Facebook's stable numeric identifier, which never changes even if the Page renames its vanity handle. Example response: ```json { "code": 200, "msg": "OK", "data": { "title": "Woodland Windows", "og": { "title": "Woodland Windows", "description": "Woodland Windows, Lisburn. 101 likes. Professional window cleaning service based in Lisburn.", "image": "https://scontent.fna.fbcdn.net/v/t39.30808-1/..." }, "stats": { "likes": 101, "followers": 0 }, "intro": "Professional window cleaning service based in Lisburn.", "email": "woodlandwindowsinfo@gmail.com", "address": "24 Woodland Avenue, Lisburn, United Kingdom, BT27 4PJ", "category": "Home window service", "reviewCount": 3, "emails": ["woodlandwindowsinfo@gmail.com"], "phones": ["+44 7926 075025"], "sourceUrl": "https://www.facebook.com/woodlandwindows1/about", "pageId": "100063628597424", "hours": "Opening soon", "priceRange": "Price range · £" } } ```

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Related