Facebook Posts
Facebook Posts are public updates from Pages, profiles, or groups, with text, links, media, author context, timestamps, and visible engagement. These content and engagement signals support campaign monitoring, editorial research, audience analysis, and reporting.
Features
- Supported public URLsCollect posts from public Facebook Page, profile, group, or post URLs through one normalized response shape.
- Content and media fieldsReturn post text, post IDs, author context, timestamps, links, media, shares, comment counts, and visible reaction counts in normalized fields.
- Reaction breakdownsProvide visible reaction breakdowns for like, love, wow, care, sad, angry, and haha.
- Requested result capAccept one or more supported URLs and use results_limit to cap the requested post records.
- Public data boundaryKeep private, restricted, login-only, or removed content outside the response boundary.
Parameters
| Parameters | Required | Description |
|---|---|---|
urls | Required | Public Facebook Page, profile, group, or post 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 an asynchronous collection task, poll its task ID, then read normalized public post records with cursor pagination.
- Prepare one or more public Facebook Page, profile, group, or post URLs.
- POST urls and an optional results_limit to /v1/facebook/posts.
- Poll /v1/tasks/{task_id} until the status is succeeded or failed.
- Read /v1/tasks/{task_id}?limit=50 and follow results.next_cursor when more records exist.
curl -X POST "https://api.socq.ai/v1/facebook/posts" \
-H "Authorization: Bearer $SOCQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{"urls":["https://www.facebook.com/cern"],"results_limit":25}'
# Poll GET /v1/tasks/{task_id}, then read /v1/tasks/{task_id}?limit=50 and use data.results.Best Use Cases
- Public page monitoring: Collect public posts, timestamps, links, media references, and visible counters from Facebook pages that your product tracks.
- Campaign and brand reporting: Normalize post text, reactions, comments, shares, and media fields before sending campaign data into dashboards or BI tools.
- Content research: Analyze public captions, post topics, links, images, videos, and engagement patterns around a brand, event, or topic.
- Social listening workflows: Route public post signals into review queues, alerting systems, or internal research tools without maintaining brittle page parsers.
- Post archive and audit trails: Store normalized post IDs, source URLs, timestamps, visible counters, and collection times for reproducible archives and reporting.
Pro Tips
- Start with small public page batches, then increase limit only after your retry and backoff behavior is working.
- Store normalized post IDs, URLs, task IDs, and next_cursor so post collection can resume after failures.
- Expect some public posts to omit comments, media, reaction details, or timestamps depending on source availability.
- Use the Comments API when you need deeper public comment threads beyond lightweight preview fields.
- Keep private, restricted, login-only, or account-owned data out of the integration assumptions unless published API docs explicitly support it.
Related APIs
Use these APIs when you need a different type of public Facebook data.
- Facebook Pages API — Retrieve public Page profiles, contact details, images, and visible audience ratings.
- 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.