Facebook Pages
Facebook Pages are public profiles for businesses, organizations, creators, and public figures, with identity, categories, descriptions, images, contact details, and audience signals. These profile and audience fields support brand discovery, directory enrichment, market research, and account comparison.
Features
- Batch Page collectionCollect one or more public Facebook Pages from Page URLs.
- Page identity and imageryReturn the Page name, category, about text, canonical URL, avatar, and cover image as normalized profile fields.
- Visible audience metricsInclude visible follower, Page-like, review, and rating metrics in a consistent metrics object.
- Public contact detailsReturn public website, email, phone, and address fields for contact and directory enrichment.
- Public data boundaryLimit results to publicly accessible Page data; private, restricted, and login-only content stays outside the response boundary.
Parameters
| Parameters | Required | Description |
|---|---|---|
urls | Required | Public Facebook Page URLs, separated by commas or new lines. |
results_limit | Optional | Maximum number of records the collection task should request. Must be a positive integer. |
How to Use
Submit a collection task, poll its task ID until processing finishes, then read normalized Page records with cursor pagination.
- Prepare one or more public Facebook Page URLs.
- POST urls and an optional results_limit to /v1/facebook/pages.
- Poll /v1/tasks/{task_id} until the status is succeeded or failed.
- Read /v1/tasks/{task_id}?limit=50 and follow results.next_cursor.
curl -X POST "https://api.socq.ai/v1/facebook/pages" \
-H "Authorization: Bearer $SOCQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{"urls":["https://www.facebook.com/Meta"],"results_limit":10}'
# Poll GET /v1/tasks/{task_id}, then read /v1/tasks/{task_id}?limit=50 and use data.results.Best Use Cases
- Brand page monitoring: Collect public Page identity, category, contact, and audience metrics for owned or competitor Page tracking.
- Page benchmark datasets: Compare Page categories, descriptions, contact coverage, follower counts, ratings, and other visible audience signals across selected Pages.
- Reporting and BI pipelines: Send normalized public Page records into dashboards, spreadsheets, warehouses, or internal review tools.
- Media archive workflows: Store Page URLs, images, descriptions, contact fields, and visible metrics for later review or reporting.
- Public social listening: Use public Page identity and audience signals to enrich social account catalogs and brand datasets.
Pro Tips
- Validate that every submitted URL resolves to a public Facebook Page before starting a large batch.
- Expect some public Pages to omit contact fields, images, ratings, or audience counters depending on result availability.
- Keep stable Page IDs and canonical URLs so jobs can be retried, audited, and deduplicated.
- Use the Facebook Posts API when your workflow needs public post records from a Page or other supported URL.
- Avoid designing workflows around private pages, restricted posts, logged-in surfaces, or account-owned data unless separate published docs explicitly support them.
Related APIs
Use these APIs when you need a different type of public Facebook data.
- Facebook Posts API — Collect public posts, media, reactions, comments, and shares from supported Facebook URLs.
- Facebook Comments API — Collect public comments, authors, engagement, media, and source links from post URLs.
Combine Facebook data with public data from other supported social platforms.