Facebook Reels Scraper (page reels, views, MP4, no login)

Scrape the public Reels and videos of any Facebook Page as a flat table — no login, no cookies, no account. One row per video with the counters brands actually track: views, reactions, comments, shares, publish date and duration, plus the caption, the thumbnail and the direct MP4 URLs.

What you get

id/videoId, url, type (reel/video), pageSlug, pageName, ownerId, description, views, viewsText, reactions, comments, shares, publishedAt (ISO 8601 UTC), durationSec, videoUrlHd, videoUrlSd, thumbnail, query, rank, source (page/url/search), detailsFetched, scrapedAt.

The owner is the publishing Page — its id, name and slug. No commenters, no reactors, no personal profiles.

Example output

Real row from the example dataset (Page nike, MP4 URLs truncated here):

Field	Example value
url	https://www.facebook.com/reel/2166091230582141/
pageName / pageSlug	Nike / nike
description	Leave your limits at the surface. #JustDoIt
views / viewsText	3300000 / 3.3M
reactions / comments / shares	7904 / 2483 / 1100
publishedAt	2025-09-15T16:01:55+00:00
durationSec	30.025
videoUrlHd	https://video-lga3-1.xx.fbcdn.net/o1/v/t2/f2/m86/AQNrPdap6OftBP5OG6byX9Zra9AIeTlJ…

Use cases

• Track a competitor's reel output and see which creatives earn the views, reactions and shares.
• Build a swipe file of top-performing reels in a niche, with the MP4 and the thumbnail attached.
• Report social performance on a schedule: monitor mode returns only what is new or what moved.

How it works

1. Page URLs → the Page's reels tab (facebook.com/<page>/reels/) is read as a logged-out visitor and every reel in it becomes a row.
2. Reel / video URLs → each reel (/reel/<id>), watch link (/watch/?v=<id>) or video permalink (/<page>/videos/<id>/) is opened directly.
3. Queries → reel permalinks indexed by a public search engine are collected for your keyword, then opened like any other video URL.
4. With fetchDetails on, every video found by (1) or (3) is opened for its own counters. Counters are always read from the payload node carrying the same video id, so a reel never inherits its neighbour's numbers.

Input

Field	Meaning	Default
pageUrls	Pages whose reels you want, e.g. https://www.facebook.com/nike	["https://www.facebook.com/nike"]
videoUrls	Known reel / watch / video permalinks to read directly	empty
queries	Keywords searched over indexed reel permalinks	empty
maxVideosPerPage	Cap of reels taken from each Page (1-200)	30
fetchDetails	Open every video for its own counters and MP4 links	true
maxItems	Stop after this many video rows	20
mode	scrape or monitor (only new/changed since last run)	scrape
monitorKey, webhookUrl, telegramBotToken, telegramChatId	Monitor-mode state key and alert targets	empty

Pricing

Event	Price
result	$0.003 per video ($3 per 1,000)
monitor-check	$0.006 per monitor run
change	$0.003 per new/changed video

Charged only for videos actually pushed. Apify platform usage (proxy, compute) is billed on top.

Why this actor

• No login and no cookies to supply — nothing to keep alive, nothing to get banned.
• Counters are matched to the video id inside the page payload, not to whatever number happens to sit nearby, so a reel never gets its neighbour's views.
• Direct HD and SD MP4 links plus the thumbnail come out of the same run.
• Monitor mode with webhook and Telegram alerts on view, reaction and comment changes.
• A run that finds nothing pushes nothing and charges no result events; the run summary explains why.

Limits

• Logged-out only. The Page's /videos/ catalogue is served empty to guests, so the listing comes from the reels tab; that tab renders a single batch (usually 6-12 reels, the most recent ones) and Facebook does not page it without a login. Use videoUrls for older videos.
• views is the exact play count where Facebook publishes one (watch pages); on a reels tab and on reel pages it is the rounded count Facebook displays (viewsText keeps the original, e.g. "2.4M"). The number in a page's Open Graph tag is cached from publication time and is used only when nothing better exists. Reels with few views carry no published count at all and come back with views: null.
• shares is published for reels, not for watch-page videos.
• No comment text, no commenters, no reactors, no followers — counts only.
• Live videos, stories and videos on private or age-restricted Pages are not available to logged-out visitors.

FAQ

Does it need a Facebook login or cookies? No. There is no account or cookie field; everything is read as a logged-out visitor, which is also why the older back catalogue is not reachable from the reels tab.

Can I download the video file? The row carries videoUrlHd and videoUrlSd, the direct MP4 URLs Facebook serves for that reel. They are time-limited signed links, so fetch them soon after the run.

What happens when there are no results? No rows are pushed and no result events are charged. The RUN_SUMMARY record in the run's key-value store carries emptyReason, separating "this Page publishes no reels" from "Facebook answered with a login wall".

Changelog

• 0.1: initial release — reels tab listing, single reel/video URLs, keyword discovery, monitor mode.

---

If this actor saved you time, a short review on its Store page genuinely helps other people find it. Found a bug or need a field that is missing? Open a ticket on the Issues tab.