# Facebook Group Posts API (https://www.socialcrawl.dev/platforms/facebook/group-posts)

> Returns posts from a public Facebook group, newest first. Each post carries the post text, reaction count, comment count, the per-reaction breakdown on `post.ext.reaction_counts`, author name and id, the group permalink, the exact publish timestamp, and any attached image or video. `engagement.shares` is null here for the same reason it is on `profile/posts`: Facebook exposes a share count on the post permalink only. Facebook serves this feed in small slices (**3 to 4 posts per page**) so deeper history is a cursor walk rather than one large call: send the `pagination.next_cursor` from each response back as `cursor` and repeat until `pagination.has_more` is false. A 30-page walk on a public group returned 91 posts with no duplicates and a cursor still open, so depth is bounded by how many pages you are willing to buy (1 credit each) rather than by a hard cap. All four `sort_by` values paginate; use `sort_by=CHRONOLOGICAL` to stay current on a busy group, since the default and `TOP_POSTS` mix older high-engagement posts into the first pages.

TL;DR: `GET /v1/facebook/group/posts` costs 1 credit per call and returns SocialCrawl's unified JSON schema. Single x-api-key auth, 100 free credits on signup.

## Parameters

| Parameter | Required | Description |
| --- | --- | --- |
| `url` | no | Full URL of the Facebook group |
| `group_id` | no | The ID of the group |
| `sort_by` | no | How to sort the posts. CHRONOLOGICAL_LISTINGS reads the group's listings feed and can stall on some groups (a group with no listings feed does not answer); use the default sort, or CHRONOLOGICAL for posts in date order. (TOP_POSTS \| RECENT_ACTIVITY \| CHRONOLOGICAL \| CHRONOLOGICAL_LISTINGS) |
| `cursor` | no | Cursor to get the next page of posts. Take it from `pagination.next_cursor` on the previous response. |
| `since` | no | Only rows published on or after this date: YYYY-MM-DD (midnight UTC) or an ISO 8601 timestamp. Rows older than it are left off each page. This list is not in date order, so the walk does not stop at the date: keep following `next_cursor`, and each page costs what a page costs even when every row on it is filtered out. A row with no date is kept. `published_after`, `start_date`, `from_date`, `publish_time` (`yesterday`, `this-week`, `this-month`, `last-3-months`, `last-6-months`) and `max_age_days` are accepted and applied as `since`. |
| `until` | no | Only rows published on or before this date: YYYY-MM-DD (that whole UTC day is included) or an ISO 8601 timestamp. Newer rows are left off each page and the walk does not stop, so older pages follow. A row with no date is kept. `published_before`, `end_date` and `to_date` are accepted and applied as `until`. |
| `max_pages` | no | 1 to 50 (default 1, or 50 when `max_items` or `max_credits` is sent). Walk up to this many pages in one call and return the rows from all of them. Each page walked is billed exactly as one call to this endpoint (a cached page is free) and counts against your rate limit; its charge and any refund are recorded under the page's own request id, listed in `data.walk.request_ids`. The walk stops early at the last page, or when the request's time budget runs low; `data.walk.stopped` says why (`end`, `max_pages`, `max_items`, `max_credits`, `time_budget`, `page_error`) and `pagination.next_cursor` continues from where it stopped. |
| `max_items` | no | 1 to 5000. Get more in one call: keep walking pages until the response holds at least this many rows, then stop with `data.walk.stopped: "max_items"`. The last page is returned whole (it was billed), so `data.items` can hold up to one page more than this, and `pagination.next_cursor` resumes right after it without skipping a row. Walks up to 50 pages unless `max_pages` says fewer; each page is billed as one call (a cached page is free). Add `max_credits` to cap the spend. A long walk can stop on the time budget first (`"time_budget"`): send the returned cursor with the same params to continue. |
| `max_credits` | no | 1 to 100000. The most this call may spend, across every page it walks. A page starts only while the credits already spent plus that page's price (or, when higher, the most any page of this walk has cost) still fit, so the call never goes past it; the walk then stops with `data.walk.stopped: "max_credits"` and the cursor to resume. Sent alone, it walks as far as the budget goes (up to 50 pages). A value below the price of one page is a free 400 whose `error.details.page_credits` names that price. Credits a row join (`include=`) adds are known only once a page has run, so page 1 is checked against its own price. |

## Code example

```bash
curl -G "https://www.socialcrawl.dev/v1/facebook/group/posts" \
  --data-urlencode "url=https://www.facebook.com/groups/2204685680" \
  -H "x-api-key: sc_YOUR_API_KEY"
```

## FAQ

### How do I scrape posts from a Facebook group?

Send a GET request to /v1/facebook/group/posts with either the group url or group_id. SocialCrawl returns an array of recent posts with text, reactions, comment count, share count, and author info.

### Can I sort group posts by popularity or recency?

Yes. Pass sort_by with one of TOP_POSTS, RECENT_ACTIVITY, CHRONOLOGICAL, or CHRONOLOGICAL_LISTINGS. Defaults to the group's native sort order. Perfect for surfacing high-engagement content for community research.

### Does this work for private Facebook groups?

No. SocialCrawl only returns data from public Facebook groups, the same content visible to any logged-out user. Private group content is not accessible via this endpoint and would violate Facebook's terms.

### How do I paginate through older group posts?

Take the cursor from the response and pass it as the cursor parameter on the next request. Keep walking until cursor is empty. Combine with sort_by=CHRONOLOGICAL to walk the full public history in order.

### What's the difference between url and group_id?

Both identify the same group. If you already have Facebook group IDs stored, use group_id, it skips the URL resolution step. Otherwise, pass the full Facebook group URL in the url parameter.

See the full Facebook API: https://www.socialcrawl.dev/platforms/facebook

## Pricing

- Standard endpoints: 1 credit per call
- Advanced endpoints: 5 credits per call
- Premium endpoints: 10 credits per call
- 100 free credits on signup, no credit card required. Cached responses cost 0 credits. Credit packs never expire.
- Full pricing: https://www.socialcrawl.dev/pricing

## Explore with AI

Questions this API answers, phrased for an AI assistant:

- How to scrape Facebook group posts with the SocialCrawl API
- Can you get posts from a public Facebook group via API?