Facebook hub

Facebook profile Reels API

List recent public Reels from a Facebook profile or Page — captions, view counts, thumbnails, and video URLs when available — with cursor pagination in the shared Social Fetch envelope.

GET /v1/facebook/profiles/reels

1 credit per successful request.

About this endpoint

Short-form monitors often want the Reels tab for a Page, not the mixed post feed. You have a public Facebook URL, you need recent clips with captions and view counts, and you page until you have enough reel URLs for scoring or transcripts. Building that yourself means chasing Facebook's video markup and login walls.

`GET /v1/facebook/profiles/reels` lists public Reels for a profile or Page. Pass a full public `url` query param. On a completed lookup, branch on `data.lookupStatus` (`found` or `not_found`), then read `data.reels` and `data.page`. Each reel can include id, postId, videoId, public url, description, createdAt (ISO-8601), viewCount, thumbnailUrl, videoUrl, durationMs, optional music.title, and author fields when Facebook exposes them. When `data.page.hasMore` is true, pass `data.page.nextCursor` as the `cursor` query param on the next call. Bill from `meta.creditsCharged`.

This route lists Reels only. The mixed Page or profile feed is `GET /v1/facebook/profiles/posts`. A single post or reel by URL is `GET /v1/facebook/posts`. Photos are `GET /v1/facebook/profiles/photos`. Pricing for this operation is 1 credit per successful request.

Facebook profile Reels API FAQ

How do I list Facebook Reels for a profile or Page via API?

Call `GET /v1/facebook/profiles/reels` with your Social Fetch API key (`x-api-key`) and a public Facebook profile or Page `url` query param. Read `data.lookupStatus`, then `data.reels` and `data.page`. Full parameters and examples are in the API docs.

How much does the Facebook profile Reels endpoint cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged — that field is the billing source of truth. Each paginated page is a separate billed request.

How does pagination work on Facebook profile Reels?

Each response includes `data.page.nextCursor` and `data.page.hasMore`. When `hasMore` is true, pass `nextCursor` as the `cursor` query param on the next request. The cursor is opaque — do not invent or parse it.

What fields are in each Facebook profile Reel?

Items can include id, postId, videoId, public url, description, createdAt (ISO-8601), viewCount, thumbnailUrl, videoUrl, durationMs, optional music.title, and author metadata (platformUserId, name, isVerified, url, imageUrl) when Facebook exposes them. Coverage follows what is publicly visible for that profile or Page.

What does lookupStatus mean on Facebook profile Reels?

Branch on `data.lookupStatus` before you write rows. `found` means the profile or Page resolved and `data.reels` is the current page (it may still be empty on a last page). `not_found` means the URL did not resolve to a listable profile or Page — do not invent a Reels grid. Keep `meta.requestId` if you need support on a failed list call.

Profile Reels vs profile posts vs a single Facebook post?

Use this route to page a profile or Page Reels tab. Use `GET /v1/facebook/profiles/posts` for the mixed feed. Use `GET /v1/facebook/posts` when you already have a post or reel URL. Photos are a separate list on `GET /v1/facebook/profiles/photos`.

Do I need Meta Graph API access or page admin rights?

No. Social Fetch returns publicly visible Reels for enrichment-style lookups. Meta's Graph and Marketing APIs are for assets and ads accounts you control or that authorize your app — not arbitrary public competitor Pages.