# Facebook Audio Downloader Reels & videos (`alpha-scraper/facebook-audio-downloader-reels-videos`) Actor

Facebook Audio Downloader Reels & videos extracts Facebook Reel and video metadata, including title, duration, description, thumbnail, and available audio download URLs. Process multiple Facebook URLs and get structured data for media research and automation.

- **URL**: https://apify.com/alpha-scraper/facebook-audio-downloader-reels-videos.md
- **Developed by:** [Alpha Scraper](https://apify.com/alpha-scraper) (community)
- **Categories:** Social media, Videos, Other
- **Stats:** 6 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

### 🎧 Facebook Audio Downloader Reels & videos – Overview

**Facebook Audio Downloader Reels & videos** is an Apify Actor for extracting useful metadata from Facebook Reels and video URLs and returning a direct audio stream URL when an audio track is available.

Instead of requiring you to manually inspect each Facebook video, this Actor accepts one or multiple Facebook URLs and processes them automatically. For each supported URL, it can return the original URL, title, duration, description, thumbnail URL, and an `audio_download_url` when an audio stream is available.

The Actor is designed for users who need structured Facebook video information together with access to an available audio stream. It is useful for research, media workflows, content analysis, archiving, and automation where Facebook Reel or video information needs to be collected in a consistent output format.

> 💡 **Facebook Audio Downloader Reels & videos**
>
> - Accept one or multiple Facebook Reel or video URLs
> - Extract video title and description when available
> - Return video duration
> - Return thumbnail information
> - Identify an available audio stream URL
> - Process multiple URLs in one Actor run
> - Return structured records for each submitted URL
> - Include an error record when a URL cannot be processed

You only need to provide the Facebook URLs in the Actor input. The Actor handles the extraction process and returns one structured result per processed URL.

### 🔊 Facebook Audio Downloader Reels & videos – Key Features

**Facebook Audio Downloader Reels & videos** focuses on a simple input-to-output workflow: provide Facebook URLs, process the media information, and receive structured metadata with an available audio URL.

#### ✅ Multiple Facebook URLs

You can submit one or many Facebook URLs through the `startUrls` input. This makes the Actor suitable for processing small collections or larger batches of Facebook Reel and video links.

Supported input examples include Facebook Reel URLs, Facebook watch URLs, Facebook shared Reel URLs, and other Facebook video URLs accepted by the underlying media extractor.

#### 🎵 Audio Download URL Extraction

A major purpose of **Facebook Audio Downloader Reels & videos** is identifying an available audio stream associated with the processed Facebook video.

The output field is named `audio_download_url`. When an appropriate audio stream is available, the Actor returns its URL instead of downloading the audio file directly into the Actor dataset.

This distinction is important: the Actor extracts the usable audio URL; it does not save an audio file to the Dataset itself.

#### 📝 Video Metadata

Alongside the audio URL, the Actor can return useful metadata associated with the Facebook media:

- Original Facebook URL
- Video title
- Video duration
- Video description
- Thumbnail URL
- Audio stream URL

Metadata availability can vary depending on the specific Facebook URL and the information exposed by the source.

#### 🖼️ Thumbnail Information

When thumbnail information is available, the Actor returns it through the `thumbnail_url` field.

This can be useful for media catalogs, content review workflows, research datasets, and systems that need a visual reference for each processed Facebook video.

> 📦 **Why Use Facebook Audio Downloader Reels & videos?**
>
> - Collect Facebook video metadata in structured records
> - Identify available audio streams
> - Process multiple Facebook URLs together
> - Reduce repetitive manual inspection
> - Build media research or content-processing workflows
> - Use the returned data in downstream automation

### 🔍 Facebook Audio Downloader Reels & videos – What Data You Can Extract

The output generated by **Facebook Audio Downloader Reels & videos** is intentionally focused on information available for each submitted URL.

| Output Field         | Description                                          |
| -------------------- | ---------------------------------------------------- |
| `url`                | The Facebook URL submitted to the Actor              |
| `title`              | Title of the processed Facebook video when available |
| `duration`           | Media duration, typically represented in seconds     |
| `description`        | Facebook video description when available            |
| `thumbnail_url`      | URL of an available thumbnail image                  |
| `audio_download_url` | Direct URL for an available audio stream             |
| `error`              | Error information when processing a URL fails        |

The normal successful output contains the first six fields. When extraction fails for a particular URL, the Actor returns the submitted URL together with an `error` field rather than silently removing that record.

#### 📊 Sample Output

A successful result can look like this:

```json
{
  "url": "https://www.facebook.com/reel/719378000556141",
  "title": "Example Facebook Reel",
  "duration": 42,
  "description": "Example video description",
  "thumbnail_url": "https://example.com/thumbnail.jpg",
  "audio_download_url": "https://example.com/audio-stream"
}
```

The exact title, description, thumbnail, duration, and media URLs depend on the Facebook content being processed.

#### ⚠️ Error Output

When an individual URL cannot be processed, the Actor records an error result for that URL.

```json
{
  "url": "https://www.facebook.com/example",
  "error": "Unable to process the requested URL"
}
```

This record-level approach makes it easier to identify problematic URLs while allowing the run to continue processing other submitted URLs.

### 🚀 Facebook Audio Downloader Reels & videos – How to Use It

Using **Facebook Audio Downloader Reels & videos** requires only a Facebook URL list.

#### 1. Add Facebook URLs

Open the Actor input and add one or more URLs to the `Start URLs` field.

You can provide Facebook Reel or video links that match the supported URL patterns exposed by Facebook.

#### 2. Run the Actor

Start the Actor after entering your URLs. Each submitted URL is processed individually.

#### 3. Review the Dataset

After processing, open the Actor's output Dataset to review the returned records.

Each successful record can contain Facebook metadata and an `audio_download_url`. Failed URLs are represented with an `error` field so you can identify them separately.

#### 4. Use the Returned Data

You can use the structured records in your own media workflow, analysis process, internal database, or automation system according to your requirements and applicable rights.

> 🛠️ **Input**
>
> - Required field: `startUrls`
> - Type: Array of URL items
> - Purpose: Provide one or multiple Facebook Reel or video URLs
> - Supported entries can be supplied as standard URL list items in the Apify input interface

### 📥 Input – What URL Should You Provide?

The current Actor configuration contains one user-facing input field:

#### `startUrls`

`startUrls` is a required array used to provide one or multiple Facebook URLs.

The field is intended for Facebook Reel and video links. The Actor processes every valid URL submitted in the list.

Example input:

```json
{
  "startUrls": [
    {
      "url": "https://www.facebook.com/watch?v=1390942842608591"
    },
    {
      "url": "https://www.facebook.com/share/r/1ANaHTYtik/"
    },
    {
      "url": "https://www.facebook.com/reel/719378000556141"
    }
  ]
}
```

You can submit a single URL or multiple URLs in the same run.

> 💡 **Input Tip**
>
> - Use complete Facebook URLs
> - Add multiple URLs when you want batch processing
> - Keep the input focused on Facebook Reel or video pages
> - Review failed records when a particular URL cannot be processed

### 🎬 How to Extract Audio Information from Facebook Reels

If your goal is to collect audio information from Facebook Reels, **Facebook Audio Downloader Reels & videos** provides an `audio_download_url` when an appropriate audio stream can be identified.

The workflow is simple:

- Add the Facebook Reel URL to `startUrls`
- Run the Actor
- Find the corresponding output record
- Check the `audio_download_url` field
- Use the returned stream URL within your permitted downstream workflow

The availability of the audio URL depends on the particular Facebook media source. Not every URL is guaranteed to expose an audio stream, and some media pages may return incomplete metadata.

The Actor therefore should be viewed as an audio-stream URL extraction tool rather than a guarantee that every Facebook video can be converted into a downloadable audio file.

### 📹 Can You Process Facebook Video URLs Without Needing Multiple Inputs?

Yes. **Facebook Audio Downloader Reels & videos** uses a single required input field, so you do not need separate fields for Reel URLs, watch URLs, or shared URLs.

Place the relevant Facebook links inside `startUrls` and process them together.

This makes the Actor useful when your source list contains different Facebook URL formats. You can maintain one input collection instead of manually separating URLs by page type.

### 🧩 Facebook Audio Downloader Reels & videos – Use Cases

The Actor can support a variety of legitimate media-data workflows.

#### 🎧 Audio Research

Researchers can collect audio stream URLs associated with publicly accessible Facebook media for analysis and permitted media workflows.

#### 📚 Content Cataloging

Media teams can build a structured catalog containing the Facebook URL, title, duration, description, thumbnail, and audio URL.

#### 🔎 Content Analysis

Analysts can collect consistent metadata from multiple Facebook videos before reviewing or processing the content in another system.

#### 🗂️ Media Inventory

Organizations maintaining a media inventory can use the structured output to track Facebook video references and associated metadata.

#### 🤖 Automation Workflows

Developers can use the Actor's structured Dataset records as an input to broader automation workflows that depend on Facebook media metadata.

#### 🔗 Batch URL Processing

When you have many Facebook Reel or video URLs, processing them together can be more convenient than opening and inspecting each URL manually.

> 📌 **Use Case Box**
>
> - Facebook Reel audio URL collection
> - Facebook video metadata extraction
> - Media research datasets
> - Content inventory preparation
> - Thumbnail and description collection
> - Batch Facebook URL processing
> - Audio-related downstream workflows

### 📤 Output – Understanding the Returned Data

**Facebook Audio Downloader Reels & videos** produces structured output records rather than an unstructured text response.

For successfully processed URLs, you can expect fields related to the source URL, media metadata, thumbnail information, and an available audio stream.

The `audio_download_url` field is especially important for workflows that need to reference the audio stream associated with the Facebook media.

However, the output should not be interpreted as a permanent media-storage location. Media URLs can depend on the source and may have availability constraints outside the control of the Actor.

### 💰 Pricing

No fixed Actor price or per-item rate is specified in the provided public Actor configuration.

The provided configuration also does not establish a guaranteed fixed cost for every Facebook URL. Actual usage costs should therefore be checked directly in the Apify platform for the current Actor and your account.

> 💳 **Pricing Note**
>
> - No invented price is listed here
> - No private billing configuration is disclosed
> - Check the Actor's current Apify pricing information for actual usage costs
> - Your total platform cost can depend on the way the Actor is run

### 💡 Tips and Best Practices

For reliable **Facebook Audio Downloader Reels & videos** runs, keep your input organized and review the returned records after processing.

#### ✅ Use Valid Facebook URLs

Start with complete Facebook URLs rather than incomplete text or copied page names.

#### ✅ Process Related URLs Together

When working with a batch, placing related Facebook Reel and video URLs in the same run can simplify dataset management.

#### ✅ Check `audio_download_url`

The presence of a successful metadata record does not necessarily mean an audio stream is available. Always check `audio_download_url` before building downstream logic around it.

#### ✅ Handle Errors

Review records containing the `error` field. Facebook content can vary, and an individual URL may fail even when other URLs in the same run work correctly.

#### ✅ Treat Media URLs as Dynamic

Returned media URLs may not behave like permanent public files. Store or process the information according to your own workflow and applicable rights.

#### 🔐 Important Usage Note

Only process and use Facebook content when you have the necessary rights, permissions, or other lawful basis to access and use the material. The Actor does not grant ownership or redistribution rights over media obtained from Facebook.

### ❓ Frequently Asked Questions

#### What is Facebook Audio Downloader Reels & videos?

**Facebook Audio Downloader Reels & videos** is an Apify Actor that processes Facebook Reel and video URLs and returns structured metadata together with an available `audio_download_url` when an audio stream can be identified.

#### Can Facebook Audio Downloader Reels & videos download an MP3 file?

The Actor does not directly create or save an MP3 file. Instead, it can return an `audio_download_url` for an available audio stream. Converting or saving that stream into another audio format requires a separate downstream process.

#### Can I process multiple Facebook Reels in one run?

Yes. The `startUrls` input is an array, so you can submit multiple Facebook Reel or video URLs in a single Actor run.

#### What Facebook data does the Actor return?

The successful output can include the submitted URL, title, duration, description, thumbnail URL, and audio download URL.

#### Does every Facebook video return an audio URL?

No guarantee is made for every URL. The `audio_download_url` depends on whether an appropriate audio stream is available for the processed media.

#### What happens when a Facebook URL fails?

The Actor creates an output record containing the submitted `url` and an `error` field. This allows you to identify unsuccessful URLs without losing the record of what was submitted.

#### Can I use Facebook Reel share links?

The input configuration is designed to accept Facebook Reel and video URLs, including share-style URLs represented in the Actor examples. Processing success can still depend on the specific source URL.

#### Does the Actor return video download files?

The Actor is focused on metadata extraction and audio stream URL extraction. Its documented output does not provide a separate video file field or a saved video file.

#### What is the easiest way to use Facebook Audio Downloader Reels & videos?

Add one or more Facebook URLs to `startUrls`, run the Actor, and review the resulting Dataset. The most relevant fields for audio-related workflows are `audio_download_url`, `title`, `duration`, and `url`.

### 🔄 Related Facebook Download Workflows

If your workflow requires a different type of Facebook media handling, related Actors may be more appropriate for the specific task.

The provided Actor configuration points users toward separate Actors for other download requirements, including a dedicated Reels Downloader and Video Downloader.

This Actor is best suited when your primary requirement is Facebook media metadata plus an available audio stream URL.

### 🆘 Support

If you encounter a problem with a Facebook URL or have questions about the Actor's behavior, review the output record first, especially the `error` field for unsuccessful items.

For Actor-related support, you can also contact the publisher directly.

- contact me by email : <alphascraper69@gmail.com>

# Actor input Schema

## `startUrls` (type: `array`):

Provide one or multiple Facebook Reels URLs

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://www.facebook.com/watch?v=1390942842608591"
    },
    {
      "url": "https://www.facebook.com/share/r/1ANaHTYtik/"
    },
    {
      "url": "https://www.facebook.com/reel/719378000556141"
    },
    {
      "url": "https://www.facebook.com/watch.bongo/videos/1554978985535088"
    }
  ]
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "startUrls": [
        {
            "url": "https://www.facebook.com/watch?v=1390942842608591"
        },
        {
            "url": "https://www.facebook.com/share/r/1ANaHTYtik/"
        },
        {
            "url": "https://www.facebook.com/reel/719378000556141"
        },
        {
            "url": "https://www.facebook.com/watch.bongo/videos/1554978985535088"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("alpha-scraper/facebook-audio-downloader-reels-videos").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "startUrls": [
        { "url": "https://www.facebook.com/watch?v=1390942842608591" },
        { "url": "https://www.facebook.com/share/r/1ANaHTYtik/" },
        { "url": "https://www.facebook.com/reel/719378000556141" },
        { "url": "https://www.facebook.com/watch.bongo/videos/1554978985535088" },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("alpha-scraper/facebook-audio-downloader-reels-videos").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "startUrls": [
    {
      "url": "https://www.facebook.com/watch?v=1390942842608591"
    },
    {
      "url": "https://www.facebook.com/share/r/1ANaHTYtik/"
    },
    {
      "url": "https://www.facebook.com/reel/719378000556141"
    },
    {
      "url": "https://www.facebook.com/watch.bongo/videos/1554978985535088"
    }
  ]
}' |
apify call alpha-scraper/facebook-audio-downloader-reels-videos --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,alpha-scraper/facebook-audio-downloader-reels-videos"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/uVrcf4OJ9VW8iCybQ/builds/u7jrtPnjBif2mu7jj/openapi.json