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

> Returns a Facebook page or profile's reels with EXACT per-reel engagement merged in: one call instead of the reels-list → post-stats chain. The plain `/v1/facebook/profile/reels` list only carries a rounded public view count ("12K" parsed back to 12000) and no likes, comments, or shares, because Facebook exposes those on the individual reel permalink only. This endpoint fetches the list, then queries each reel's permalink server-side and overwrites the item's `engagement` with the exact figures: `views` (the rounded list value is replaced), `likes`, `comments`, and `shares`. `saves` stays null (Facebook exposes no public save count), and `comments` can be null on a zero-comment reel (a quirk of the permalink upstream). Per-item `ext.engagement_source` is `"post_detail"` when the exact figures landed and null when that reel's lookup failed (the item then keeps the honest list values); read `engagement_coverage` before grading, and `_warnings: ["engagement_partial"]` flags a partial page. Billing: a flat 5 credits per page of 10 reels (1 credit for the list + 4 for the per-reel enrichment, roughly half the cost of running the chain yourself); if enrichment yields zero coverage the 4-credit premium is refunded automatically. Paginate with `next_cursor`, or pass `limit` (1-50) to have the endpoint walk pages server-side until it has collected that many reels, billed per page consumed.

TL;DR: `GET /v1/facebook/profile/reels/full` costs 5 credits per page of 10 reels - 1 for the list and 4 for the per-reel enrichment - which is roughly half what running the list-then-post-stats chain yourself costs. With no `limit` that is one page and a flat 5 credits. With `limit` set the endpoint walks `ceil(limit / 10)` pages, up to 5 for the 50 maximum (25 credits), holds that many up front and refunds every page it did not need. A page whose enrichment yields zero coverage refunds the 4-credit premium automatically, leaving the 1-credit list price 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. |
| `cursor` | no | Cursor from a prior response's next_cursor to page deeper. |
| `limit` | no | Return up to this many reels in one call (1-50). The endpoint pages the underlying list server-side until it has collected this many (or runs out), and bills per upstream page consumed (5 credits/page of 10). If the walk hits the internal time budget first, the response carries `_warnings: ["walk_deadline_reached"]`, unfetched pages are refunded, and `next_cursor` resumes where it stopped. Omit for a single page. |

## Code example

```bash
curl -G "https://www.socialcrawl.dev/v1/facebook/profile/reels/full" \
  --data-urlencode "url=https://www.facebook.com/Meta" \
  -H "x-api-key: sc_YOUR_API_KEY"
```

## FAQ

### How do I get exact counts from the Facebook reels views API?

Send a GET request to /v1/facebook/profile/reels/full with the page or profile URL in url. SocialCrawl fetches the reels list, looks up each reel's permalink on the server and replaces the rounded list figure with exact views, likes, comments and shares.

### Why not use the plain Facebook reels API?

The plain /v1/facebook/profile/reels list carries only Facebook's rounded public view count, such as 12K parsed back to 12000, and no likes, comments or shares. This endpoint merges the per-reel figures in, so you do not run the list and a post lookup for every reel yourself.

### What does each reel in the response contain?

Each item is a post with its id, url, description text, thumbnail, duration, author and publish time, plus engagement.views, likes, comments and shares. saves is null because Facebook publishes no public save count, and ext.engagement_source reads post_detail when the exact figures landed.

### How much does the Facebook reels views endpoint cost?

It bills 5 credits per page of 10 reels, which covers the list and the per-reel lookups. Pass limit (1 to 50) to collect more reels in one call, up to 25 credits; pages it did not need are refunded, and if no reel on a page gets exact figures, the lookup part of the price is refunded automatically.

### How do I page through all of a page's reels?

Send data.next_cursor back as cursor for the next page, or set limit and let the endpoint walk pages on the server until it has that many reels. If a long walk runs out of time, the response carries walk_deadline_reached, unfetched pages are refunded, and next_cursor resumes where it stopped.

### How do I know every reel got exact numbers?

Read engagement_coverage before you compare reels, and check _warnings for engagement_partial, which flags a page where some lookups failed. A reel whose lookup failed keeps the list values and has ext.engagement_source set to null.

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 can I get exact view counts for Facebook reels with the SocialCrawl API?
- Which SocialCrawl endpoint returns likes, comments and shares for every reel on a Facebook page?