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

> Returns Facebook page or profile reels as unified Post items. Each item includes a reel ID, description, thumbnail, duration when available, author identity, `engagement.views` when the upstream provides it, permalink, and publish time. Likes, comments, shares, and saves remain null because this endpoint does not expose those counts. **Two caveats worth knowing before you grade on these numbers:** (1) `engagement.views` here is Facebook's ROUNDED public display value (the "12K" / "2.6M" the page shows, parsed back to a number: e.g. 12000 where the true count is 12366), not an exact count; (2) the upstream carries no per-reel engagement beyond that view count. A third, on pagination: on a page with only a handful of reels the first response can report `pagination.has_more: true` and the next page then come back empty, because the upstream mints a cursor it cannot fill. The empty page is free, so this costs a round trip rather than a credit. For EXACT views plus likes, comments, and shares, the easiest path is `GET /v1/facebook/profile/reels/full`, which runs this list and the per-reel lookups server-side and merges the exact engagement in (flat 5 credits per page of 10 reels). Alternatively, take each item's `post.url` and pass it to `/v1/facebook/post` (single) or batch up to 100 of them into `POST /v1/prism/post-stats` (1 credit per successful URL, dead links refunded).

TL;DR: `GET /v1/facebook/profile/reels` 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` | yes | Full URL of the Facebook page or profile. A profile share link (`https://www.facebook.com/share/…`) is accepted. |
| `next_page_id` | no | To paginate through to the next page |
| `cursor` | no | To paginate through to the next page |
| `recent_days` | no | Keep only reels published in the last N days (1 to 3650) and stop pagination once a page reaches older reels. Does not change the price of a page. |
| `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/profile/reels" \
  --data-urlencode "url=https://www.facebook.com/Meta" \
  -H "x-api-key: sc_YOUR_API_KEY"
```

## FAQ

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

Send a GET request to /v1/facebook/profile/reels with the page url. SocialCrawl returns each reel with view count, reaction count, comment count, thumbnail URL, video URL, and publish timestamp.

### Can I download the reel videos?

The response includes direct video URLs hosted by Facebook. You can stream them, download them for archival, or pass them into video analysis pipelines. Note that Facebook's video URLs may expire, refresh before long-term use.

### How do I paginate through older reels?

Take the cursor or next_page_id from the response and pass it back as cursor on the next request. Walk until cursor is empty. This surfaces the full public reels history in reverse-chronological order.

### Is view count included?

Yes. Each reel returns its current view count, the same number shown on Facebook. Great for benchmarking short-form content performance, tracking competitor reach, or building creator analytics dashboards.

### Do I need the new Facebook Graph API v19+?

No. SocialCrawl does not require any Graph API version or access token. The endpoint reads publicly available reels data directly, no app review, no OAuth, just your SocialCrawl x-api-key.

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 reels with an API
- Does SocialCrawl return view counts for Facebook reels?