Facebook Reels Scraper | Page Reels & Metrics
Pricing
$3.00 / 1,000 reels
Scrape public Facebook Page Reels and direct Reel URLs. Export engagement metrics, captions, creators, dates and optional media URLs to JSON, CSV or Excel. Filter by date and deduplicate results without a Facebook login.
All notable changes to this Actor are documented in this file.
v2.1 stabilization: makes delivered records carry what the README promises (engagement counts, owner identity), repairs operational truth, and adds the competitor-proven exact-count mode (experimental). Implemented from the v2.1 spec; live findings from the 2026-09-03 v2.1 probe and live cloud test report.
![Facebook Groups Scraper – Posts, Comments & Replies [No Login]✅ avatar](https://images.apifyusercontent.com/sob6rjYjL3ShSSWyz1HN65Wkft8htqd3bcxP7JAgWUo/rs:fill:76:76/cb:1/aHR0cHM6Ly9hcGlmeS1pbWFnZS11cGxvYWRzLXByb2QuczMudXMtZWFzdC0xLmFtYXpvbmF3cy5jb20vc0NDU2R3bm1LTUoxUTJzVG4tYWN0b3ItYTBkbUdoNTJFNHloNXVuN2gtTGdvRnlWbzVYTi1pbWdiaW4tbG9nby1mYWNlYm9vay1pY29uLWZhY2Vib29rLWxvZ28tdHJhbnNwYXJlbnQtZmFjZWJvb2stbG9n.webp){kind=avatar}
viewCount/reactionCount (+ display/label/precision/source) with source: "open_graph" and precision: "rounded" (or "exact" for full numbers). Unobserved channels stay null — never 0.ownerType/ownerName/ownerUrl derived from the 4-segment og:url/canonical page-video shape at zero extra requests; profile-shaped URLs classify as profile; unresolvable shapes stay unknown.dateFrom/dateTo accept YYYY-MM-DD, full ISO timestamps, and relative expressions ("7 days", "2 months", "1 year") resolved against run start in UTC, matching the official actor's UX.metricsMode: "exact" (ticket 10, experimental): requests direct-Reel details in a locale proven (2026-09-03 probe) to serve unabbreviated counters ("6.4K views" → "6.492 Aufrufe"); German dot-grouped numbers and labels parse locale-aware. Precision labels always reflect the observed display string; promotion from experimental requires the Phase 0 exact-agreement gates.sourceLocale now carries the observed og:locale (e.g. en_US).INTERNAL_ERROR failure code for unclassified exceptions so block-rate telemetry stays trustworthy (ticket 01).PARSER_DEGRADATION warnings that actually fire: systemic schema-miss rate above threshold, or zero candidates on every attempted Page after browser escalation (ticket 01).RUN_REPORT warning; the run fails (INVALID_INPUT_URL) only when zero valid sources remain, with an aggregated, capped rejection message.SUCCEEDED/EMPTY/CHARGE_LIMIT still exit 0.RUN_REPORT.totals (excludedBeforeRange, excludedAfterRange, unresolvedTimestamp), so emitted + excluded + unresolved reconciles with attempted.provenOptionalMediaFields re-baselined through the standard pipeline — only thumbnailUrl survives on current logged-out pages.EMPTY + PARSER_DEGRADATION + per-source stop reasons). Repair is an evidence-gated follow-up (see the probe report §3).BROWSER_FALLBACK) violated Apify storage naming rules (lowercase letters, digits, hyphens only). The queue is now run-scoped (browser-fallback-<runId>), which also prevents aborted runs from leaking browser work into later runs. Discovered by the first live cloud run of v2 on 2026-09-03; local runs never hit it because local storage does not enforce the naming rule.saveErrors: true runs crashed on the first recorded error because the named dataset ERROR_RECORDS also violated the naming rule. The dataset is now named error-records (README and docs updated accordingly).extractReelIdFromUrl now resolves the numeric Reel ID from Facebook's modern 4-segment /videos/<descriptive-slug>/<id>/ og:url/canonical shape. Previously it returned the descriptive slug, so direct-Reel records were discarded with PARSER_SCHEMA_MISS even though the page carried extractable OpenGraph data.JS_REQUIRED and escalates once to the bounded browser fallback (per-source attempt ledger), instead of silently reporting "no more public results" with no verification. Facebook client-side renders Reels grids for logged-out visitors on all HTML surfaces. Browser requests are now counted in RUN_REPORT.requests.browserRequests.This major release delivers an HTTP-first architecture overhaul designed for high throughput, predictable memory footprint (1,024 MB baseline), granular metric precision, and seamless Pay-Per-Event (PPE) integration.
HOLD.seed_and_direct_only finite pagination route under the current Phase 0 HOLD decision as recorded in Phase 0 Decision. Deep page history pagination remains unproven.schemaVersion: "2.0.0". All nested objects (author, page, audio, fieldStatus) are replaced with a flat 53-field schema for zero-transformation analytics and direct CSV export compatibility.canonicalUrl is replaced by url.publishedAt is replaced by createdAt (with companion createdAtTimestamp and createdAtPrecision).caption is replaced by text.author.* and page.* are flattened into ownerType (page, profile, unknown), ownerName, ownerId, ownerUrl, and sourcePageUrl.audio.* is flattened into musicTitle and musicArtist.play: playCount, playCountDisplay, playCountLabel, playCountPrecision, playCountSourceview: viewCount, viewCountDisplay, viewCountLabel, viewCountPrecision, viewCountSourcereaction: reactionCount, reactionCountDisplay, reactionCountLabel, reactionCountPrecision, reactionCountSourcecomment: commentCount, commentCountDisplay, commentCountLabel, commentCountPrecision, commentCountSourceshare: shareCount, shareCountDisplay, shareCountLabel, shareCountPrecision, shareCountSourcenull and are never coerced to 0. A value of 0 strictly indicates that Facebook explicitly published an observed zero count.maxListingScrolls and maxConcurrency are removed. Concurrency and pagination are handled automatically by the HTTP crawler engine and bounded browser resource pool.dedupeKey (facebook:reel:<reelId>) across all records for at-least-once downstream reconciliation.videoUrlSd, videoUrlHd, thumbnailUrl, mediaUrlObservedAt, and mediaUrlMayExpire: true for short-lived CDN URLs.RUN_REPORT persisted to the default Key-Value Store with per-source progress counters, parser health rates, and warnings. Dedicated ERROR_RECORDS dataset available when saveErrors: true.videoUrlSd, videoUrlHd, thumbnailUrl) are signed CDN URLs that may expire after several hours (mediaUrlMayExpire: true). Downstream pipelines should download or ingest media promptly.This hardening release follows a ten-perspective production-readiness review. It adds a separate candidate-detail budget for narrow date ranges, strengthens Reels-only URL admission, binds hydration metadata to the target Reel identity, preserves mixed source-kind provenance, bounds browser snapshot capture, adds deterministic response-capture draining, emits sanitized debug diagnostics, rejects detail pages that no longer resolve to a Reel, and expands parser/deduplication regression coverage.
The release also upgrades and pins the production browser runtime to the matching Apify Node 22 / Playwright 1.62.1 image, moves the TypeScript runtime loader into production dependencies, and verifies zero production dependency advisories with npm audit --omit=dev.
Pre-publication fixes folded into this release: the request-handler timeout now scales with maxListingScrolls so default discovery runs no longer exceed the previous fixed 180-second budget; malformed URL strings inside captured hydration JSON no longer crash detail parsing; profile.php?id=… Page sources normalize to the correct sk=reels listing target; zero-millisecond durations parse as 0 instead of falling through to unrelated keys; and dead failure-classification branches were removed. Platform-side schema files were corrected for Apify build validation: unsupported per-field advanced flags were removed from the input schema, and the dataset schema was restructured to the required actorSpecification/fields/views shape with a full record schema. Dataset schema field types were then aligned with the emitted records (mediaUrlExpiryWarning is boolean-or-null and reelId is nullable), push failures now log the platform rejection reason and a sanitized record type signature, and a CI contract test validates fixture, fully populated, and sparse records against the deployed schema.
The initial production release adds public-only Facebook Reel collection from Page/Profile discovery URLs and exact direct Reel URLs. It provides a 1,000-result default, configurable limit through 10,000, exact inclusive UTC date bounds, canonical URL deduplication, public metadata normalization, aggregate engagement counters, transient-media warnings, source-level diagnostics, and RUN_REPORT coverage reporting.
The release includes a Node.js 22 TypeScript/Playwright Apify Actor, strict runtime input validation, Console input/output schemas, durable queue/checkpoint behavior, sanitized error records, fixture-based tests, and deployment documentation.