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

> Returns a list of recent posts from a Facebook page or profile. Each post includes the post text, like count, comment count, media attachments, the publish timestamp, and the per-reaction breakdown on `post.ext.reaction_counts` (`[{type, count}]`, highest first). Facebook publishes a post's share count, and a reel's exact view count and duration, on the individual post only, not on the feed, so on a plain call `post.engagement.shares` is null on every row and `post.engagement.views` and `post.content.duration_seconds` are null on reels. Send `include=engagement` and every row is joined, in the same call, to the per-post lookup that carries them: the share count lands on each row, and the exact view count and duration on each reel. The reaction counts and the publish time the feed already carries are never replaced, and a row that links to an event rather than a post is not looked up. Cost: 1 credit for the page plus 1 credit per row filled from a fresh lookup (3 rows a page, so 4 credits at most); rows already in cache are filled for free, rows that could not be filled are refunded, and a repeat of the same call within the cache window is 0 credits. Time: `include=engagement` adds 2 to 7 seconds on a fresh page (the lookups run in parallel and the call waits for the slowest, never more than 12 seconds) and nothing when the rows are already cached. The response carries a `hydration` block itemising rows, lookups, cache hits, credits and milliseconds. Facebook serves this feed in small slices, so the first response is a window onto the page rather than everything it has: `pagination.page_size` reports how many posts that window held, and deeper history is a cursor walk. Send `pagination.next_cursor` back as `cursor` and repeat until `pagination.has_more` is false; each page costs 1 credit (plus the join when you ask for it), so depth is bounded by how many pages you buy. `recent_days=N` keeps only posts from the last N days and ends the walk once a page reaches older posts; it does not change the price of a page.

TL;DR: `GET /v1/facebook/profile/posts` costs 1 credit for the page. include=engagement holds 1 credit per row (3 rows a page) and keeps only the rows filled from a fresh lookup, so a page is at most 4 credits; rows served from cache are free, unfilled rows are refunded, and a repeat of the same call within the cache window costs 0. With `max_pages`, `max_items` or `max_credits`, each page walked is billed at this price (a cached page is free), and `max_credits` caps the total. and returns SocialCrawl's unified JSON schema. Single x-api-key auth, 100 free credits on signup.

## Parameters

| Parameter | Required | Description |
| --- | --- | --- |
| `since` | no | Only posts published on or after this date: YYYY-MM-DD (midnight UTC) or an ISO 8601 timestamp. Older posts are left off the page, and the page that reaches one ends the walk: `next_cursor` is not returned and `pagination.stopped_at` is `since`. Pinned posts sit out of date order and never end the walk. The page still costs what a page costs, so a daily poll pays for the pages it walks and no more. |
| `stop_at_id` | no | The id (`post.id`) or URL (`post.url`) of the newest post you already hold. The page stops just before it: that post and everything after it are left off, `next_cursor` is not returned, and `pagination.stopped_at` is `known_id`. A pinned post never counts as the stop point. If it is not on this page the page is returned in full with its cursor, so keep walking. `pagination.stopped_at` is `end` when the list ran out first and `null` while there is more to walk. |
| `url` | no | Full URL of the Facebook page or profile to fetch posts for. A profile share link (`https://www.facebook.com/share/…`) is accepted. |
| `pageId` | no | Facebook profile page id |
| `cursor` | no | To paginate through the posts |
| `include` | no | Set to `engagement` (one token only) to fill `post.engagement.shares` on every row, and `post.engagement.views` and `post.content.duration_seconds` on reels, in this one call. Holds 1 credit per row (3 a page) and keeps only the rows filled from a fresh lookup: rows already in cache and rows the lookup cannot fill are refunded, and a row with no public share count stays null and is free, so a page is never more than 4 credits and the usual bill is lower. A row that links to an event rather than a post is not looked up. The join takes 2 to 7 seconds on a fresh page, never more than 12, and nothing when the rows are already cached; read `data.hydration` for the rows, the credits held and kept, and the time. Without it the call is unchanged. (engagement) |
| `recent_days` | no | Keep only posts published in the last N days (1 to 3650) and stop pagination once a page reaches older posts. Does not change the price of a page. |
| `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/profile/posts" \
  --data-urlencode "url=https://www.facebook.com/Meta" \
  -H "x-api-key: sc_YOUR_API_KEY"
```

## FAQ

### How do I list posts from a Facebook page?

Send a GET request to /v1/facebook/profile/posts with either url or pageId. SocialCrawl returns an array of recent posts including text, like count, comment count, the per-reaction breakdown, media attachments, and publish timestamp. Add include=engagement and the share count lands on every row in the same call.

### What fields does each post include?

Every post has its id, text content, like count, comment count, publish timestamp, author info, and any media attachments (images, videos, links). Facebook keeps the share count off the feed and publishes it on the post itself, so pass include=engagement to fill post.engagement.shares on every row. Field names stay consistent across all SocialCrawl platforms.

### How do I paginate through older posts?

Take the cursor value from the response and pass it as the cursor parameter on the next request. Repeat until the cursor is empty. You can walk through hundreds of posts without hitting the Graph API's pagination limits.

### Can I use pageId instead of the page URL?

Yes. The endpoint accepts either url or pageId as the identifier. If you already have Facebook page IDs in your database, pass pageId directly, it's slightly faster than resolving the URL on each request.

### Does the endpoint return video posts and reels?

Yes, video and reel posts appear in the response with their media URLs. A reel's exact view count and duration sit on the reel itself rather than on the feed, so add include=engagement to fill both on every reel row. For reels-specific data, use /v1/facebook/profile/reels. For a dedicated photo feed, use /v1/facebook/profile/photos.

### What does include=engagement cost and how long does it take?

The page is 1 credit, plus 1 credit for each row filled from a fresh lookup, so a page tops out at 4 credits. Rows already in cache are filled for free and rows the lookup could not fill are refunded. The join adds 2 to 7 seconds on a fresh page and nothing when the rows are cached, and data.hydration itemises the rows, the credits, and the milliseconds.

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 list Facebook page posts with an API
- What data does SocialCrawl return for Facebook posts?
- How to get Facebook post share counts without a call per post