Facebook Reels Scraper
Pricing
$5.99/month + usage
Facebook Reels Scraper
π¬β¨ Facebook Reels Extractor β Seamlessly capture, organize & transform Reels into clean, ready-to-use data ππΌ. Works locally or in the cloud βοΈπ», supports secure browsing π, proxies π & custom limits π―. Streamlined output for analytics & automation β‘π.
Pricing
$5.99/month + usage
Rating
5.0
(4)
Developer

Neuro Scraper
Actor stats
0
Bookmarked
31
Total users
12
Monthly active users
20 days ago
Last modified
Categories
Share
πΉ Facebook Reels Scraper Actor
Effortlessly extract structured metadata from Facebook Reels directly on the Apify platform.
π Summary
This Actor takes one or more Facebook Reels URLs and produces structured JSON with details such as title, uploader, view counts, dates, and more. Only Reels are processed β other video types are skipped.
π‘ Use cases
- Social media analytics dashboards
- Content performance tracking
- Archiving structured metadata for further research
- Automating reporting on trending Reels
β‘ Quick Start (Apify Console)
-
Go to your Actor in Apify Console.
-
Click Run.
-
In the Input tab, paste JSON like:
{"startUrls": [{"url": "https://www.facebook.com/reel/1234567890123456"}],"maxItems": 10} -
Click Run β results will appear in the default Dataset.
β‘ Quick Start (CLI & API)
CLI (apify-cli)
$apify run -p input.json
Where input.json contains:
{"startUrls": [{"url": "https://www.facebook.com/reel/1234567890123456"}]}
API (apify-client in Python)
from apify_client import ApifyClientclient = ApifyClient('<APIFY_TOKEN>')run = client.actor('<ACTOR_ID>').call(run_input={"startUrls": [{"url": "https://www.facebook.com/reel/1234567890123456"}],"maxItems": 5})# Fetch dataset itemsfor item in client.dataset(run["defaultDatasetId"]).iterate_items():print(item)
π Inputs
startUrls(array of objects or strings) β List of Facebook Reel URLs. Required.cookiesFile(string, optional) β Path to uploaded cookies file. Useful if login is required.proxyConfiguration(object, optional) β Proxy settings as provided in Apify Console.maxItems(integer, optional) β Maximum number of items to scrape.
βοΈ Configuration
| π Name | π Type | β Required | βοΈ Default | π Example | π Notes |
|---|---|---|---|---|---|
startUrls | array | β Yes | null | [ {"url": "https://facebook.com/reel/..."} ] | URLs of Reels to scrape |
cookiesFile | string | β No | null | cookies.txt | Upload via Apify key-value store |
proxyConfiguration | object | β No | {} | { "useApifyProxy": true } | Configure via Console proxy tab |
maxItems | integer | β No | 0 (no limit) | 50 | Limit results processed |
ALL_RESULTS | dataset | Auto | n/a | Dataset tab | Full consolidated results stored in key ALL_RESULTS |
β‘οΈ Example: In Apify Console β Input, paste:
{"startUrls": [ {"url": "https://www.facebook.com/reel/1234567890123456"} ]}
π€ Outputs
- Each Reel produces a JSON object with fields like:
{"platform": "facebook","content_type": "reel","webpage_url": "https://www.facebook.com/reel/1234567890123456","id": "1234567890123456","title": "Sample Reel","uploader": "Page Name","view_count": "2.3K","like_count": 150,"comment_count": 20,"timestamp_iso": "2025-09-10T12:34:56Z","thumbnail": "https://...jpg"}
- Consolidated results are stored under key
ALL_RESULTSin the Key-Value Store.
π Environment variables
APIFY_TOKENβ Required to call the Actor via API or CLI.HTTP_PROXY/HTTPS_PROXYβ Only if using custom external proxies.
βΆοΈ How to Run
In Apify Console
- Open Actor β Run.
- Configure input JSON in Input tab.
- Click Run.
CLI
$apify call <ACTOR_ID> -p input.json
API
See the Python example above under Quick Start (API).
β° Scheduling & Webhooks
- In Console β Schedule, set periodic runs (e.g., every hour).
- Add webhooks in Console β Webhooks to notify when a run succeeds/fails.
π Logs & Troubleshooting
-
View logs in the Run detail page.
-
Common issues:
No startUrls provided.β EnsurestartUrlsfield is set.- Empty dataset β The URL was not a Reel, or access required login/cookies.
π Permissions & Storage
- Results go to the default Dataset and
ALL_RESULTSkey in the Key-Value Store. - If using cookies, store them securely in Apify key-value storage.
π Changelog / Versioning
- Increment Actor version when input/output schema changes.
π Notes / TODOs
- TODO: Confirm if
cookiesFilemust be uploaded to default key-value store or passed differently. - TODO: Clarify maximum recommended
startUrlsper run (performance consideration).
π Proxy configuration
-
In Apify Console β Run β Proxy, enable Apify Proxy.
-
To use custom proxies: in Actor settings β Environment variables, add:
HTTP_PROXY = http://<USER>:<PASS>@<HOST>:<PORT>HTTPS_PROXY = http://<USER>:<PASS>@<HOST>:<PORT>
-
Never hardcode credentials β store them as secrets.
-
TODO: Advanced proxy rotation patterns may be added.
π References
π§ What I inferred from main.py
- Actor strictly processes Facebook Reels, skips other videos.
- Inputs:
startUrls,cookiesFile,proxyConfiguration,maxItems. - Outputs pushed to Dataset and consolidated in Key-Value store under
ALL_RESULTS. - Network requests are made β included Proxy configuration section.
- Assumptions marked TODO for cookies handling and max
startUrlsbatch size.