Facebook Reels Scraper

Extracts structured metadata from public Facebook Reels. The actor scrapes embedded video information and returns clean JSON, suitable for content analysis, monitoring, or data pipelines.

Key Features

• Metadata Extraction: Fetches video details including ID, title, description, upload date, duration, and counts for comments/reposts.
• Media Info: Retrieves available video and audio formats (SD, HD, DASH), thumbnails, and automatic captions in multiple languages.
• Uploader Data: Provides uploader name, ID, and platform information.
• Proxy Strategy: Uses a No-proxy-first approach, falling back to Apify Proxy (RESIDENTIAL) if needed to bypass blocks.
• Flexible Input: Accepts a single video URL, a list of URLs (urls), or startUrls via the Request List Editor for batch processing.
• Structured Output: Pushes one dataset item per video and saves a complete JSON array to the key-value store under the key OUTPUT.

How to Use

Provide the actor with Facebook Reel URLs. It's designed for batch scraping and integrates with Apify datasets for automation.

Accepted Input Parameters:
* url: A single video URL (string).
* urls: An array of video URLs (array of strings).
* startUrls: An array of request objects, typically used via the Request List Editor in the Apify console.

Input / Output

Example Input:

{
  "startUrls": [
    { "url": "https://www.facebook.com/reel/785977587505597" },
    { "url": "https://www.facebook.com/share/r/1Cvc1uotQb/" }
  ]
}

Output Structure:
The actor outputs a JSON array. Each item contains these main sections:

Example Output Snippet:

[
  {
    "id": "1394880385139005",
    "title": "Example Reel Title...",
    "webpage_url": "https://m.facebook.com/watch/?v=1394880385139005",
    "uploader": "User Name",
    "formats": [ ... ]
  }
]

Troubleshooting

• Empty Dataset: Ensure the Reel URL is public. Enable the RESIDENTIAL proxy in your run configuration if you encounter blocks.
• Partial Metadata: Some fields (like comment counts) are only included if they are present in the page's embedded data. Absence of a field is normal in these cases.
• Failures/Timeouts: Network blocks are common. Use Apify Proxy (RESIDENTIAL), consider increasing timeouts, or enable sticky sessions.
• Actor Input Not Found: Verify your input uses one of the accepted parameters (startUrls, url, or urls).