Facebook Group Posts API

Facebook Group Posts

Features

• Public group URL batchesAccept one or more public Facebook group URLs and preserve the originating group URL with every normalized post record.
• Four group ordering modesUse top_posts, recent_activity, chronological, or chronological_listings to select the ordering applied across submitted groups.
• Per-group collection depthApply results_limit separately to each group URL, with a default of 100 and an accepted range from 3 through 2,000.
• Post and author contextReturn post IDs, source URLs, message text, author IDs and names, publication times, and collection times in a consistent structure.
• Visible engagement and videoInclude visible reaction, comment, and video view counts plus normalized video and thumbnail URLs when a public post exposes them.

Parameters

How to Use

Submit public group URLs with optional ordering and a per-group result limit, then read the asynchronous task results with cursor pagination.

1. Prepare one or more public Facebook group URLs.
2. POST urls with optional results_limit and sort_by to /v1/facebook/group-posts, then store the returned task_id.
3. Poll /v1/tasks/{task_id} until the task succeeds or returns a failure.
4. Read data.results.items and request the returned next_cursor while has_more remains true.

curl -X POST "https://api.socq.ai/v1/facebook/group-posts" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"urls":["https://www.facebook.com/groups/1270525996445602/"],"results_limit":30,"sort_by":"recent_activity"}'

# Poll GET /v1/tasks/{task_id}
# Read data.results.items and follow next_cursor while has_more is true

Best Use Cases

• Public group activity review: Use recent_activity or chronological ordering with message, author, created_at, and group_url fields to review public updates from selected groups.
• Group discussion archives: Store post IDs, message text, author context, source URLs, publication times, and collection times as attributable public group records.
• Aligned engagement comparison: Apply the same sort_by across group URLs and compare reactions_count, comments_count, and views_count under one ordering.

Pro Tips

• Submit direct public group URLs rather than a group name so every input remains tied to an unambiguous source.
• Calculate requested depth as the number of urls multiplied by results_limit because the limit applies separately to each group.
• Run separate tasks when comparing ordering modes because one sort_by value is applied to every group URL in a request.
• Retain id and extra.group_url together so downstream records remain attributable and can be deduplicated within each group.
• Treat author, message, publication time, video media, and video view counts as optional when a public post does not expose them.
• Follow results.next_cursor until has_more is false when the completed task contains more than one result page.

Related APIs