# Pinterest Video Downloader (`alpha-scraper/pinterest-video-downloader`) Actor

Pinterest Video Downloader extracts publicly accessible Pinterest video and image data from one or more Pin URLs. Get video and image URLs, thumbnails, titles, descriptions, uploader details, engagement stats, dimensions, duration, and structured metadata in an easy-to-use dataset.

- **URL**: https://apify.com/alpha-scraper/pinterest-video-downloader.md
- **Developed by:** [Alpha Scraper](https://apify.com/alpha-scraper) (community)
- **Categories:** Videos, Social media, SEO tools
- **Stats:** 2 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

### Pinterest Video Downloader

Pinterest Video Downloader extracts publicly accessible Pinterest media information from one or more Pinterest Pin URLs and returns structured metadata together with video or image access URLs. It is designed for users who need Pinterest video data, media URLs, thumbnails, dimensions, descriptions, uploader information, statistics, and related Pin metadata in a structured Apify dataset.

The Actor accepts Pinterest URLs through the `startUrls` input, including standard Pinterest Pin links and `pin.it` links. Each submitted URL is processed independently, and the resulting record is saved to the default dataset.

For video Pins, the output can include available video qualities, media URLs, dimensions, duration, and thumbnail information. For image Pins, the Actor returns an image URL with its width and height. The Actor also returns common Pin metadata such as ID, title, description, webpage URL, uploader information, statistics, board information, and media resolution.

### What Is the Pinterest Video Downloader?

The Pinterest Video Downloader is a Pinterest data extraction tool focused on publicly accessible Pin media and metadata. Rather than requiring users to manually inspect individual Pins, it converts supported Pinterest URLs into structured records that can be reviewed or processed as part of a larger workflow.

The Actor is useful when the goal is to collect Pinterest video links, image URLs, Pin metadata, uploader details, engagement statistics, and media properties in a consistent format.

A typical workflow is:

`Pinterest Pin URL → Actor processing → Structured Pin metadata and media URLs → Apify Dataset`

The Actor does not require users to manually define individual fields for every Pin. You provide one or more supported Pinterest URLs, start the run, and receive a separate result for each processed URL.

### Key Features

| Feature                   | Description                                                                  | User Benefit                                                         |
| ------------------------- | ---------------------------------------------------------------------------- | -------------------------------------------------------------------- |
| Pinterest URL processing  | Accepts one or multiple Pinterest URLs through `startUrls`.                  | Process individual Pins or multiple Pins in one run.                 |
| Video data extraction     | Returns available video-related information and video URLs for video Pins.   | Makes Pinterest video media information easier to collect and reuse. |
| Image data extraction     | Identifies image Pins and returns image URL and dimensions.                  | Supports media collection beyond video-only Pins.                    |
| Pin metadata              | Extracts identifiers, title, description, webpage URL, and related metadata. | Provides structured context for each collected Pin.                  |
| Uploader information      | Returns available uploader ID, username, and full name fields.               | Helps connect media records with their source profile information.   |
| Statistics                | Returns available repin, comment, like, and view values.                     | Supports basic Pinterest engagement analysis.                        |
| Thumbnail information     | Includes the available thumbnail URL.                                        | Makes it easier to reference preview media.                          |
| Media dimensions          | Returns width, height, resolution, and video duration when available.        | Helps with media classification and downstream processing.           |
| Structured dataset output | Saves each processed result as a dataset item.                               | Provides consistent records for analysis and automation.             |

### What Data Can You Extract?

The Pinterest Video Downloader returns a structured record for each submitted URL. The available information is organized into several useful groups.

**Pin information**

Each successful record can contain the Pin ID, media type, title, description, SEO-oriented title value, creation date when available, domain/extractor information, original webpage URL, and submitted URL.

**Uploader information**

The `uploader` object contains available uploader identifiers and names. The returned structure includes an uploader ID, username, full name, and follower count field. The follower count may remain `0` when that information is not available from the source data.

**Engagement statistics**

The `stats` object contains available values for repins, comments, likes, and views. It also includes a `share_count` field and a `total_saves` value derived from the available repin and like data.

**Video information**

For video Pins, the Actor can return multiple available video representations. Each video entry can include quality, media URL, width, height, and duration in milliseconds. A thumbnail URL is also included when available.

**Image information**

For image Pins, the `downloads.image` array can contain the image URL together with width and height.

**Media properties**

At the top level, the record can also include duration, width, height, and a resolution value such as `720x1280`.

### Why Use the Pinterest Video Downloader?

Collecting Pinterest Pin information manually can become repetitive when multiple URLs need to be reviewed. The Pinterest Video Downloader provides a structured workflow where submitted URLs are processed and stored as individual dataset records.

This is useful for:

- Organizing Pinterest media references in a dataset.
- Collecting video and image URLs from public Pins.
- Capturing descriptive metadata together with media information.
- Supporting research and content-analysis workflows.
- Creating structured datasets for later filtering or analysis.
- Reducing repetitive manual copying of Pin information.
- Processing multiple supplied Pinterest URLs in one Actor run.

The resulting dataset can be used as a starting point for analysis, cataloging, research, media organization, or other workflows that operate on structured Pin records.

### How to Use the Pinterest Video Downloader

Using the Actor requires only the supported Pinterest URLs.

1. Open the Actor in Apify.
2. Enter one or more Pinterest Pin URLs in the **Start URLs** input.
3. Check that each URL points to the Pinterest content you intend to process.
4. Start the Actor.
5. Review the resulting dataset.
6. Use the structured media URLs and metadata in your downstream workflow.

The input accepts Pinterest URLs in the configured request-list format. The supplied examples demonstrate both a `pin.it` short link and a localized Pinterest web URL.

For large collections, it is practical to begin with a small test run so you can verify that the supplied URLs produce the type of records you expect.

### Input

The Actor has one required input field: `startUrls`.

| Field       | Type  | Required | Description                                                 |
| ----------- | ----- | -------- | ----------------------------------------------------------- |
| `startUrls` | Array | Yes      | List of one or more Pinterest video or Pin URLs to process. |

The input is configured as a request-list source, so each entry represents a Pinterest URL. The Actor accepts entries supplied as URL objects and also handles string URLs during processing.

Supported examples shown in the configuration include `pin.it` links and Pinterest web URLs such as `pinterest.com` or localized Pinterest domains.

### Input Example

```json
{
  "startUrls": [
    {
      "url": "https://pin.it/52mnGKjoi"
    },
    {
      "url": "https://fr.pinterest.com/pin/866309678468834338/"
    }
  ]
}
```

Use actual publicly accessible Pinterest URLs when configuring your run. Do not add unsupported fields because they are not part of the Actor's documented input schema.

### Output

Each successfully processed URL produces a structured dataset record. Failed URL processing is also represented as a record containing the submitted URL and an `error` field.

The output structure is divided into top-level Pin information, uploader data, statistics, board information, and media/download information.

For video Pins, `downloads.video` contains available video entries. For image Pins, `downloads.image` contains image information.

### Output Fields

| Field         | Description                                                            |
| ------------- | ---------------------------------------------------------------------- |
| `id`          | Pinterest Pin or extracted media identifier.                           |
| `type`        | Detected media type, such as `video` or `image`.                       |
| `title`       | Available Pin title.                                                   |
| `description` | Available Pin description.                                             |
| `seo_title`   | Full title when available, otherwise the regular title.                |
| `created_at`  | Available upload/creation date value.                                  |
| `domain`      | Extractor/domain information returned with the source data.            |
| `webpage_url` | Pinterest webpage URL associated with the result.                      |
| `uploader`    | Object containing available uploader information.                      |
| `stats`       | Object containing available engagement statistics.                     |
| `board`       | Board-related fields included in the output structure.                 |
| `downloads`   | Object containing video or image media information and thumbnail data. |
| `duration`    | Media duration when available.                                         |
| `width`       | Media width when available.                                            |
| `height`      | Media height when available.                                           |
| `resolution`  | Combined width and height representation.                              |
| `url`         | Original submitted Pinterest URL.                                      |
| `error`       | Error message when processing that URL fails.                          |

### Output Example

A video result can resemble the following structure:

```json
{
  "id": "866309678468834338",
  "type": "video",
  "title": "Example Pinterest Video",
  "description": "Example Pin description",
  "seo_title": "Example Pinterest Video",
  "created_at": "20260919",
  "domain": "Pinterest",
  "webpage_url": "https://www.pinterest.com/pin/866309678468834338/",
  "uploader": {
    "id": "example-user",
    "username": "example-user",
    "full_name": "Example User",
    "follower_count": 0
  },
  "stats": {
    "repin_count": 10,
    "comment_count": 2,
    "share_count": 0,
    "like_count": 15,
    "total_saves": 25
  },
  "board": {
    "id": "",
    "name": "",
    "url": "",
    "privacy": "public"
  },
  "downloads": {
    "video": [
      {
        "quality": "720p",
        "url": "https://example.com/video.m3u8",
        "width": 720,
        "height": 1280,
        "duration_ms": 15000
      }
    ],
    "thumbnail": "https://example.com/thumbnail.jpg"
  },
  "duration": 15,
  "width": 720,
  "height": 1280,
  "resolution": "720x1280",
  "url": "https://pin.it/52mnGKjoi"
}
```

The example values above are illustrative. Actual returned values depend on the supplied Pinterest Pin and the information available for that Pin.

### Use Cases

The Pinterest Video Downloader can support several practical workflows involving public Pinterest media and metadata.

**Content research:** Collect Pinterest Pin titles, descriptions, media references, and related metadata for research projects.

**Media cataloging:** Build a structured collection of video and image references with dimensions, duration, and thumbnails.

**Market research:** Analyze public Pinterest content and available engagement statistics across a selected set of Pins.

**Dataset creation:** Transform a list of Pinterest URLs into structured records suitable for later filtering, analysis, or organization.

**Competitive research:** Review publicly accessible Pin metadata, uploader information, media properties, and engagement indicators.

**Content analysis:** Combine descriptive information and media properties with other research datasets.

**Automation workflows:** Use the dataset output as structured input for downstream processes that operate on Pinterest content records.

### Advantages

The Actor combines media-related information with contextual metadata instead of returning only a single media URL. This can make the resulting records more useful for workflows that need both the media reference and information about the corresponding Pin.

Another practical advantage is support for multiple supplied URLs in a single run. Each URL is handled independently, allowing the resulting dataset to contain separate records that can be reviewed or analyzed individually.

### Limitations

Results depend on the information that is publicly accessible for each submitted Pinterest URL. Not every Pin necessarily exposes every metadata field.

Some uploader statistics may be unavailable, in which case the corresponding returned value may be empty or zero. Board-related fields can also remain blank because the available source information does not always contain populated board details.

For video Pins, available video representations and media URLs may vary. The Actor extracts accessible media information rather than guaranteeing that every Pin provides identical video qualities or metadata.

The Actor returns media access URLs and metadata; it does not describe a guaranteed file-download or re-encoding result for every Pinterest Pin.

### Pros and Cons

| Pros                                                  | Cons                                                                |
| ----------------------------------------------------- | ------------------------------------------------------------------- |
| Processes one or multiple Pinterest URLs.             | Metadata availability can vary by Pin.                              |
| Returns structured video and image information.       | Some uploader and board fields may be unavailable.                  |
| Includes useful Pin metadata and statistics.          | Video formats and available qualities may differ.                   |
| Saves results as structured dataset records.          | A failed URL is returned with an error rather than guaranteed data. |
| Supports both short and standard Pinterest URL forms. | Results depend on publicly accessible source information.           |

### Comparison With Alternative Approaches

| Capability                     | This Actor                 | Manual / Typical Alternative        |
| ------------------------------ | -------------------------- | ----------------------------------- |
| URL-based processing           | Supported                  | Usually manual                      |
| Multiple supplied URLs         | Supported                  | Often repetitive                    |
| Structured metadata            | Returned as dataset fields | May require manual collection       |
| Video media references         | Included when available    | Often copied individually           |
| Image media references         | Included for image Pins    | Often handled separately            |
| Uploader and statistics fields | Included where available   | Requires separate manual review     |
| Dataset-oriented workflow      | Built into the Actor run   | May require additional organization |

This comparison describes workflow differences rather than a universal advantage over every alternative method.

### Competitive Advantages

The Pinterest Video Downloader provides a focused workflow around Pinterest Pin URLs and produces more context than a media link alone. A single record can combine media references with Pin metadata, uploader information, statistics, dimensions, duration, and webpage information.

The structured output also makes the results easier to work with programmatically or review as a dataset. Multiple URLs can be supplied through the same input field, helping users organize batches of Pinterest content without creating separate configurations for every Pin.

### Best Practices

Start with a small group of Pinterest URLs before processing a larger collection. This lets you confirm that the submitted links correspond to the intended Pins and that the returned fields suit your workflow.

Use direct, valid Pinterest URLs and review the resulting records for the metadata you actually need. Because source information can vary between Pins, avoid assuming that every field will be populated for every record.

For research or analysis, validate important media and metadata values before treating them as authoritative business or analytical data.

When processing multiple URLs, keep your input organized so that each submitted address can be traced back to the corresponding output record.

### Troubleshooting

**Invalid Input**

Check that `startUrls` is an array and that each entry contains a valid Pinterest URL. Use the configured request-list structure shown in the input example.

**Empty or Missing Results**

Verify that the submitted URL is publicly accessible and points to the intended Pinterest content. Some Pins may expose less information than others.

**Partial Metadata**

Fields such as uploader statistics, board information, engagement counts, or media properties may not be available for every Pin. An empty or zero value does not necessarily indicate that the Pin contains no underlying activity; it may simply mean that the requested information was not available.

**Video Information Not Available**

A Pinterest URL may resolve to content that is identified as an image rather than a video, or the available source data may not provide the expected video representations. Check the returned `type` and `downloads` object.

**Processing Error**

When a URL cannot be processed successfully, the dataset can contain the submitted `url` together with an `error` field. Review the URL and retry with a valid publicly accessible Pinterest link when appropriate.

### Frequently Asked Questions

**What does the Pinterest Video Downloader do?**

It processes public Pinterest URLs and returns structured Pin metadata together with available video or image media information.

**What URLs can I submit?**

The configured input accepts Pinterest URLs, including examples using `pin.it` short links and Pinterest web URLs.

**Can I process multiple Pinterest Pins in one run?**

Yes. The `startUrls` input is an array, so you can provide multiple URL entries in the same Actor run.

**What data does the Pinterest Video Downloader return?**

Depending on the Pin, results can include Pin ID, title, description, webpage URL, uploader information, statistics, thumbnails, video or image URLs, dimensions, duration, and resolution.

**Does it return Pinterest video URLs?**

For video Pins, the `downloads.video` section can contain available video media URLs and associated quality and dimension information.

**Does it also process images?**

Yes. The Actor determines whether the extracted media is a video or image and can return image information for image Pins.

**Does every Pin contain the same metadata?**

No. Available metadata can vary. Some uploader, board, engagement, or media fields may be empty or unavailable for certain Pins.

**What happens when a URL fails?**

The resulting record can contain the original `url` and an `error` field describing the processing failure.

**Is the output structured for data workflows?**

Yes. Each processed result is pushed as a dataset item with consistent top-level fields and nested objects for uploader, statistics, board, and media information.

**Should I test a few URLs first?**

Yes. A small test run is useful for confirming that your Pinterest URLs and expected output fields match your intended workflow before processing a larger collection.

### NLP Keywords

- Pinterest video downloader
- Pinterest video scraper
- Pinterest Pin data extraction
- Pinterest video extraction
- Pinterest media downloader
- Pinterest media scraper
- Pinterest Pin scraper
- Pinterest video URL extraction
- Pinterest image extraction
- Pinterest Pin metadata
- Pinterest video metadata
- Pinterest thumbnail extraction
- Pinterest uploader data
- Pinterest engagement data
- Pinterest video links
- Pinterest image URLs
- Pinterest structured data
- Pinterest content extraction
- Pinterest dataset creation
- Pinterest media data

### Related Keywords

- download Pinterest videos
- Pinterest video download links
- extract Pinterest video URLs
- scrape Pinterest Pin URLs
- Pinterest video metadata extractor
- Pinterest public media scraper
- Pinterest Pin information extractor
- Pinterest image and video scraper
- Pinterest media URL extractor
- Pinterest content data scraper
- Pinterest Pin metadata scraper
- extract Pinterest Pin data
- Pinterest video research tool
- Pinterest media data extraction
- Pinterest video collection
- Pinterest dataset scraper
- scrape public Pinterest content
- Pinterest video link extractor
- Pinterest media information
- Pinterest Pin data collector

### Final Overview

The Pinterest Video Downloader provides a focused way to turn publicly accessible Pinterest Pin URLs into structured media and metadata records. Users can submit one or more Pinterest URLs and receive information covering available Pin details, uploader data, engagement statistics, media URLs, thumbnails, dimensions, duration, and resolution.

Its output is designed for practical dataset-oriented workflows such as media cataloging, content research, market research, competitive research, dataset creation, and automated data processing. Because the available information can differ between Pins, users should review returned records and validate important values before relying on them for critical analysis.

The Actor is most useful when the goal is to collect Pinterest media references and contextual Pin information in a consistent, structured format rather than manually reviewing each URL.

**Contact me:** <Alphascraper69@gmail.com>

# Actor input Schema

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

List of one or more Pinterest video URLs

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://pin.it/52mnGKjoi"
    },
    {
      "url": "https://fr.pinterest.com/pin/866309678468834338/"
    }
  ]
}
```

# 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://pin.it/52mnGKjoi"
        },
        {
            "url": "https://fr.pinterest.com/pin/866309678468834338/"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("alpha-scraper/pinterest-video-downloader").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://pin.it/52mnGKjoi" },
        { "url": "https://fr.pinterest.com/pin/866309678468834338/" },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("alpha-scraper/pinterest-video-downloader").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://pin.it/52mnGKjoi"
    },
    {
      "url": "https://fr.pinterest.com/pin/866309678468834338/"
    }
  ]
}' |
apify call alpha-scraper/pinterest-video-downloader --silent --output-dataset

```

## MCP server setup

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

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/xHu3nR7GmEGKFZ8Yb/builds/78xp5hW6cN5GKKv6r/openapi.json