📌 Pinterest Pins, Videos & Search Scraper Plus

Pinterest Scraper — Extract Pins, Videos and Engagement Data

Pinterest Pins, Videos & Search Scraper Plus turns a keyword, or a pin/board/profile URL, into typed JSON rows for every pin Pinterest serves back — image and video variants, board and pinner objects, hashtags, and save/comment/reaction counts. Unlike scrapers that fold every input into a keyword search, this Actor routes pin, board, and profile URLs to their real Pinterest endpoint and records how in the output mode field. Every response is flat, typed JSON — ready for a database, a spreadsheet, or an LLM context window without an HTML-parsing step. This guide covers every input and output field, how the deterministic bookmark paging and engagement-count enrichment work, and three ways teams put it into production.

🧭 What Does Pinterest Pins, Videos & Search Scraper Plus Do?

Pinterest Pins, Videos & Search Scraper Plus scrapes public Pinterest pins — standalone images, video pins, and the pins inside a board or profile feed — using unauthenticated, browser-driven requests against Pinterest's own public pages. It requires no Pinterest login, account, or API token: every input is either a keyword (routed to Pinterest search) or a real Pinterest URL (a pin, a board, or a profile), and each is scraped through the endpoint Pinterest itself would serve that content from.

• 🔍 Real URL routing — a pin URL, board URL, or profile URL is detected and scraped through its own endpoint, not collapsed into a keyword search; the mode field on every row records which path was used
• 📌 Full pin data — title, description, canonical pinUrl, creation timestamp, dominant color, domain, and outbound link
• 🖼️ Every image size — all size variants Pinterest exposes, in an images object, plus a selectable primary imageUrl
• 🎥 Video pin detail — duration, audio flag, every MP4/HLS variant, thumbnail, and a selectable primary videoUrl
• 💾 Engagement data — save (repin) count, comment count, and per-type reaction counts with human-readable labels, all optional per run via includeCounts
• 📋 Board and pinner objects — structured board metadata (name, privacy, pin/follower counts) and pinner identity (username, verified status, follower count) embedded on every pin
• #️⃣ Hashtags and pin tags — parsed locally from the title/description text, no extra request

⚡ Features & Capabilities

Pinterest Pins, Videos & Search Scraper Plus is built around three things: real routing instead of keyword-only search, complete per-pin field coverage, and deterministic paging that doesn't silently drop results.

Core features

• Real mode detection. detect_mode() in the Actor's source parses each searchTerms entry: a bare keyword becomes a search; a /pin/{id}/ URL becomes pin; a /{username}/{board-slug}/ URL becomes board; a /{username}/ URL becomes profile. Every output row carries the resolved mode and the original sourceUrl, so you can confirm exactly how each input was interpreted.
• Deterministic bookmark paging. Feed targets (search/board/profile) scroll and capture Pinterest's own paginated XHR responses, then — if maxItems isn't reached by scrolling — replay the same feed request with Pinterest's resource_response.bookmark cursor (up to 40 additional pages) instead of relying on scroll position alone, so paging doesn't stall or silently under-deliver.
• One flat row per pin, every field named. Every pin — image or video — produces the same 36-key row shape: type, isChild, pinId, pinUrl, mode, title, description, createdAt, imageUrl, imageSize, width, height, images, dominantColor, saveCount, repinCount, commentCount, reactionCounts, reactionsLabeled, totalReactions, isVideo, isRepin, videoUrl, videoDuration, videoHasAudio, videoThumbnail, videoVariants, board, pinner, hashtags, pinTags, domain, link, searchTerm, sourceUrl, scrapedAt.
• Opt-in engagement enrichment. Save and comment counts aren't in Pinterest's search/board/profile feed payload — enabling includeCounts fetches each pin's public closeup page (one extra page load per pin, run through a pool of up to 3 concurrent browser pages) and parses saveCount/commentCount out of the embedded relay data. A single pin URL gets counts for free, since its closeup page is already loaded to scrape the pin itself.
• Cross-target de-duplication. A single run can mix keywords, pin URLs, board URLs, and profile URLs; a global_seen set tracks pin IDs across every target in the run so the same pin is never pushed twice even if two targets surface it.

How Pinterest Pins, Videos & Search Scraper Plus compares to other Pinterest scrapers

Feature	Pinterest Pins, Videos & Search Scraper Plus	simpleapi/pinterest-pins-videos-search-scraper	scrapapi/pinterest-pins-videos-search-scraper
Image data	All size variants in an images object, selectable primary via imageSize	Single url field at one fixed size, no size-variant object shown in their documented output (observed on the Apify Store, 2026-07-26)	Same single-url pattern, no size variants (observed on the Apify Store, 2026-07-26)
Video pins	Full videoVariants (MP4 + HLS) with duration, audio flag, thumbnail, selectable primary videoUrl	Single link_to_video field only, no variant list, duration, or audio flag documented (observed 2026-07-26)	Same single link_to_video field (observed 2026-07-26)
Save & comment counts	Explicit saveCount/repinCount and commentCount fields, opt-in via includeCounts	No comment-count field in the documented output; only an unlabeled reaction_counts object (observed 2026-07-26)	Same as simpleapi — no dedicated save/comment fields documented (observed 2026-07-26)
Board & pinner detail	Structured board object (id, name, url, privacy, pin/follower counts) plus a richer pinner (id, verified, follower count, URL)	No board object in the documented output; pinner limited to full_name/username/follower_count/image_url (observed 2026-07-26)	Same limited pinner shape, no board object (observed 2026-07-26)
URL routing	Pin/board/profile URLs are detected and routed to their own endpoint; mode on every row records it	Input accepts a profile URL, but the documented output schema has no mode/routing field (observed 2026-07-26)	Same — no routing field documented (observed 2026-07-26)
Pricing model	Pay per event (pin_result)	Flat monthly price (observed 2026-07-26)	Pay per event, same model (observed 2026-07-26)

If your use case is feeding structured data to an LLM or a database, the field-depth rows are the decision-maker: a single unlabeled url and link_to_video string means every consumer downstream re-derives image quality and video-variant choice for itself, which is extra logic to write and maintain rather than a solved problem.

When another tool might suit you better

If all you need is a large volume of keyword-searched pins with basic image/pinner fields — no board data, no comment counts, no URL routing for pins/boards/profiles — scrapestorm's flat $9.90/month listing (observed on the Apify Store, 2026-07-26) is a simpler, cost-predictable option for high-volume, low-per-item-value runs, since it charges a fixed monthly fee rather than per result. This Actor is the better fit once you need board/profile input, video-variant detail, or engagement counts, since those aren't in scrapestorm's documented output.

Pinterest Pins, Videos & Search Scraper Plus within the Scrapio data stack

This is currently the only Pinterest Actor in the Scrapio lineup — it covers pins, videos, boards, and profiles in one Actor rather than splitting them across separate tools. For other platforms in the same stack: Instagram Hashtag Scraper covers Instagram posts by hashtag, Facebook Reels Scraper Plus covers Facebook's short-video format with the same engagement-analytics pattern, and TikTok Trending Scraper covers trending short-form video on TikTok.

Why do developers and data teams scrape Pinterest?

🏢 E-commerce and marketing teams

Retail and marketing teams feed searchTerms with product-category keywords or a competitor's board/profile URL, cap maxItems, and enable includeCounts to see which pins are actually driving saves. saveCount, totalReactions, and domain (the outbound link's domain) together show which visual styles and which outbound sites are getting traction for a given search term or board, without manually opening dozens of pins.

📊 AI training data and RAG indexing

title, description, and hashtags are the highest-information text fields per pin — description is often longer and more descriptive than a typical social caption, and hashtags are already parsed into an array rather than left embedded in text. For RAG enrichment, index description alongside pinUrl, board.name, and pinner.username so a retrieval hit traces back to its source pin and board. For training data, isVideo, hashtags, totalReactions, and saveCount form a consistently typed feature set: every field is a typed primitive (string, number, boolean, or array), not a display string requiring parsing.

📱 Competitive and market intelligence

Track a competitor's board or profile on a schedule and diff on pinId to catch new pins, or on saveCount/totalReactions (with includeCounts on) to catch which existing pins are gaining traction. domain reveals which external sites a competitor is consistently driving traffic to through their pins.

🔬 Research and academic use

Visual-content and social-platform research can build a structured pin dataset from public search results, boards, or profiles at scale. Every field documented here comes from content Pinterest serves to an unauthenticated visitor — no private boards, password-protected profiles, or login-gated content are accessible to this Actor.

🎥 Product and SaaS development

Because output is a stable, flat 36-key row, it's a direct fit for a trend-monitoring dashboard, a mood-board aggregation tool, or a content-licensing lead tool built on scheduled runs. imageUrl/videoUrl give a downstream product directly usable media URLs without re-deriving them from Pinterest's page markup.

🍚 Input Parameters

All parameters below are read directly from .actor/actor.json's input schema — names, types, defaults, and constraints are reproduced exactly.

Parameter	Required	Type	Description	Example Value
searchTerms	Yes	array (stringList)	Keywords or real Pinterest URLs — a pin, a board, or a profile URL. URLs are routed to the correct endpoint, not turned into a keyword search.	["cat", "https://www.pinterest.com/pin/60376016447291956/"]
maxItems	No	integer (min 1, max 1000, default 50)	Maximum pins to scrape per input target (keyword/board/profile). A single pin URL always returns 1. Deterministic bookmark paging is used to reach this number without dropping results.	50
filtre	No	string (enum All/Videos, default All)	All returns pins and videos; Videos returns only video pins.	"All"
imageSize	No	string (enum orig/736x/564x/474x/236x, default orig)	Which image variant fills the primary imageUrl field. All variants are always returned in the images object; this only selects the primary. orig is the original full resolution.	"orig"
videoFormat	No	string (enum auto/mp4/hls, default auto)	Which video variant fills the primary videoUrl field for video pins. All variants are always returned in videoVariants. auto prefers a direct MP4, then HLS.	"auto"
includeCounts	No	boolean (default false)	Fetches each pin's save (repin) count and comment count. These aren't in Pinterest's search/board/profile grid data, so enabling this makes one extra request per pin — slower and more compute on large runs. A single pin URL always includes counts for free.	true
proxyConfiguration	No	object (proxy editor)	Proxy settings. By default no proxy is used; if Pinterest blocks the request, the Actor falls back to datacenter, then residential proxies automatically.	{"useApifyProxy": false}

Example input

{
  "searchTerms": [
    "cat",
    "https://www.pinterest.com/pin/60376016447291956/",
    "https://www.pinterest.com/nasa/"
  ],
  "maxItems": 50,
  "filtre": "All",
  "imageSize": "orig",
  "videoFormat": "auto",
  "includeCounts": false,
  "proxyConfiguration": { "useApifyProxy": false }
}

Supported URL types and input formats

searchTerms accepts a mix of the following, one entry per array item:

• A plain keyword — "cat" or "minimalist kitchen". Anything not starting with http is routed to Pinterest search (mode: "search").
• A pin URL — "https://www.pinterest.com/pin/60376016447291956/" (also matches /pin/{slug}--{id}/). Scrapes exactly that one pin (mode: "pin"), including counts for free.
• A board URL — "https://www.pinterest.com/username/board-name/". Scrapes the pins on that board's own feed (mode: "board").
• A profile URL — "https://www.pinterest.com/username/" (also matches /username/_saved/ and /username/_created/ sub-tabs). Scrapes that profile's pin feed (mode: "profile").

📦 Output Format

Every pin is pushed as one flat JSON row to the Apify dataset. The dataset's default view surfaces all 36 fields the row-building code writes — build_pin_record() in src/main.py — so there are no hidden extra fields beyond what the view shows.

Output for Pins

{
  "type": "pin",
  "isChild": false,
  "pinId": "60376016447291956",
  "pinUrl": "https://www.pinterest.com/pin/60376016447291956/",
  "mode": "pin",
  "title": "silly kitty",
  "description": "how i feel when i order the wrong color yarn",
  "createdAt": "2025-09-17T21:05:25",
  "imageUrl": "https://i.pinimg.com/originals/46/f4/88/46f4885495c1ed7ca2dbfd4787b06bb6.jpg",
  "imageSize": "orig",
  "width": 736,
  "height": 1104,
  "images": {
    "236x": { "url": "https://i.pinimg.com/236x/46/f4/88/....jpg", "width": 236, "height": 354 },
    "474x": { "url": "https://i.pinimg.com/474x/46/f4/88/....jpg", "width": 474, "height": 711 },
    "orig": { "url": "https://i.pinimg.com/originals/46/f4/88/....jpg", "width": 736, "height": 1104 }
  },
  "dominantColor": "#88a549",
  "saveCount": 120,
  "repinCount": 120,
  "commentCount": 3,
  "reactionCounts": { "1": 1877, "5": 4 },
  "reactionsLabeled": { "love": 1877, "haha": 4 },
  "totalReactions": 1881,
  "isVideo": false,
  "isRepin": false,
  "videoUrl": null,
  "videoDuration": null,
  "videoHasAudio": null,
  "videoThumbnail": null,
  "videoVariants": {},
  "board": {
    "id": "1023456789012345",
    "name": "Cats",
    "url": "https://www.pinterest.com/username/cats/",
    "privacy": "public",
    "pinCount": 240,
    "followerCount": 18,
    "isCollaborative": false
  },
  "pinner": {
    "id": "998877665544332",
    "full_name": "Sofia Ortiz",
    "username": "sofiacamposflor",
    "url": "https://www.pinterest.com/sofiacamposflor/",
    "follower_count": 4,
    "verified": false,
    "image_url": "https://s.pinimg.com/images/user/default_140.png"
  },
  "hashtags": [],
  "pinTags": [],
  "domain": "instagram.com",
  "link": "https://www.instagram.com/reel/DEhTvQWMgfw/",
  "searchTerm": "60376016447291956",
  "sourceUrl": "https://www.pinterest.com/pin/60376016447291956/",
  "scrapedAt": "2026-07-26T00:00:00Z"
}

Output for Video Pins

Video pins carry the same 36-key row, with isVideo: true and the video-specific fields populated instead of null/empty:

{
  "isVideo": true,
  "videoUrl": "https://v1.pinimg.com/videos/mc/720p/22/0a/21/220a2175b12eb3752b6f1826a52e412f.mp4",
  "videoDuration": 14320,
  "videoHasAudio": true,
  "videoThumbnail": "https://i.pinimg.com/videos/thumbnails/220a2175b12eb3752b6f1826a52e412f.jpg",
  "videoVariants": {
    "V_720P": { "url": "https://v1.pinimg.com/videos/mc/720p/....mp4", "width": 720, "height": 1280, "thumbnail": "https://i.pinimg.com/....jpg" },
    "V_HLSV3_MOBILE": { "url": "https://v1.pinimg.com/videos/iht/hls/....m3u8", "width": 0, "height": 0, "thumbnail": "" }
  }
}

videoUrl is chosen from videoVariants by videoFormat: auto/mp4 picks the highest-width entry among MP4 (V_*, non-HLS) variants and falls back to HLS if none exist; hls does the reverse. All variants Pinterest returns stay in videoVariants regardless of which one is selected as primary.

Output for Engagement & Board Data

The same row also carries engagement and provenance fields worth calling out on their own: saveCount/repinCount (Pinterest's "repin" is the same action as a save — the two fields are aliases of one number) and commentCount are null in feed modes unless includeCounts is true; a single pin URL always has them populated. reactionCounts is Pinterest's raw {reaction_id: count} object; reactionsLabeled maps the known IDs (1=love, 2=thanks, 3=good_idea, 4=wow, 5=haha) to names and falls back to reaction_<id> for any unmapped ID; totalReactions sums them. board is null when a pin isn't attached to a visible board; pinner is always an object, empty-stringed where Pinterest doesn't expose a field for that pinner.

Schema stability and export options

All 36 fields are present on every row regardless of pin type — a null or empty value replaces a missing field rather than the key being dropped, so downstream consumers can rely on a fixed schema across a run that mixes image and video pins. Results are stored in the Actor's default Apify dataset and can be exported from the Apify Console or API in JSON, CSV, Excel, XML, or HTML, or fetched programmatically via apify_client.

💡 Pinterest Pins, Videos & Search Scraper Plus Strategy Guide

🎯 Strategy 1: Real-time enrichment pipeline

Trigger a run whenever a new product URL, competitor board, or profile enters your system — pass it as a searchTerms entry with a tight maxItems and includeCounts: true. Read the finished dataset via the Apify API, then write saveCount, totalReactions, and domain back onto the source record as a social-proof or referral-traffic signal.

🎯 Strategy 2: Scheduled monitoring and alerting

Set up an Apify schedule to run the same board/profile searchTerms list daily or weekly. Diff each run's output against the previous one on pinId to detect new pins, and on saveCount/totalReactions for existing pins to catch which ones are gaining traction. Alert on the delta that matters — a new pinId for content teams, a jump in saveCount for a brand-monitoring workflow.

🎯 Strategy 3: Bulk dataset build

For a research or training corpus, feed a large searchTerms list (mixing keywords, board URLs, and profile URLs) in a single run, or split it across several parallel runs. Set maxItems up to the schema's 1000 maximum per target and export the combined dataset to CSV or push it into a database via the Apify API's dataset endpoints. No concurrency limit on simultaneous Actor runs is documented for this Actor; any limit you hit would come from your Apify plan's memory/run concurrency, not from this Actor's code.

Strategy comparison at a glance

Strategy	Best for	Run pattern	Output format
Real-time enrichment	Social-proof or referral-traffic scoring on new records	On-demand, single-target, low maxItems	JSON via API, written back to source system
Scheduled monitoring	Competitor/board tracking over time	Recurring Apify schedule, same searchTerms each run	JSON/CSV, diffed run-over-run
Bulk dataset build	Research corpora, training data	One large run or several parallel runs	CSV/JSON export or direct database load

🌴 Related Pinterest Scrapers & Tools

Scraper	What it extracts
Instagram Hashtag Scraper	Instagram posts, likes, and comments by hashtag
Facebook Reels Scraper Plus	Facebook's short-video format, with the same optional engagement-analytics pattern
TikTok Trending Scraper	Trending short-form video data on TikTok, with trend insights
Twitter Profile & Tweets Scraper	Tweets and profile data from Twitter/X
Website Contact & Email Extractor	Contact details from an outbound link's own domain — useful for enriching a pin's link/domain fields

How to integrate Pinterest Pins, Videos & Search Scraper Plus with your stack

Pinterest Pins, Videos & Search Scraper Plus works with any language or tool that can make an HTTP request to the Apify API. The examples below use the actor name from .actor/actor.json: pinterest-pins-videos-search-scraper-plus.

Python

from apify_client import ApifyClient
import csv

client = ApifyClient("<APIFY_API_TOKEN>")

run = client.actor("pinterest-pins-videos-search-scraper-plus").call(run_input={
    "searchTerms": [
        "cat",
        "https://www.pinterest.com/pin/60376016447291956/",
    ],
    "maxItems": 50,
    "filtre": "All",
    "imageSize": "orig",
    "videoFormat": "auto",
    "includeCounts": True,
})

rows = list(client.dataset(run["defaultDatasetId"]).iterate_items())

with open("pins.csv", "w", newline="", encoding="utf-8") as f:
    writer = csv.DictWriter(f, fieldnames=rows[0].keys())
    writer.writeheader()
    writer.writerows(rows)

print(f"Saved {len(rows)} pin rows to pins.csv")

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<APIFY_API_TOKEN>' });

const run = await client.actor('pinterest-pins-videos-search-scraper-plus').call({
    searchTerms: ['cat', 'https://www.pinterest.com/nasa/'],
    maxItems: 50,
    includeCounts: true,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(`Fetched ${items.length} pins`);
items.forEach(p => console.log(p.pinId, p.mode, p.saveCount));

Async and scheduled pipelines

For large searchTerms lists, call the Actor via apify_client's .start() method instead of .call() to fire the run and return immediately, then poll the run status or subscribe to the run's webhook to know when the dataset is ready. For recurring collection, use an Apify schedule rather than a self-managed cron job — it runs this Actor with the same input on a fixed interval without you hosting anything.

🎯 Who Needs Pinterest Pins, Videos & Search Scraper Plus? (Use Cases & Industries)

🏢 E-commerce and marketing teams

Pull pins for a product-category keyword or a competitor's board, and report saveCount, totalReactions, and domain per pin to see which visual styles and outbound links are performing — without manually reading Pinterest's own UI counters.

📊 AI and data engineering teams

Index title, description, and hashtags for RAG retrieval over a search term's or board's pin history, or use the full 36-field row set as a consistently typed feature table for a classification or recommendation model.

📱 Competitive intelligence analysts

Track a set of competitor boards or profiles on a schedule and flag new pinId values or rising saveCount/totalReactions on existing pins.

🔬 Researchers

Build a public-data pin dataset for visual-content or social-platform research across as many public search terms, boards, or profiles as your searchTerms list covers; every field traces back to content Pinterest serves to an unauthenticated visitor.

🎥 SaaS and product builders

Use imageUrl/videoUrl plus the full field set as the data layer for a trend-monitoring dashboard, a content-curation tool, or a lead-generation product built on scheduled runs, without self-hosting scraping infrastructure.

Is it legal to scrape Pinterest?

Scraping publicly accessible web pages is generally lawful in the United States — the Ninth Circuit's hiQ Labs v. LinkedIn (2019, reaffirmed 2022) held that scraping data a website makes available without a login does not violate the Computer Fraud and Abuse Act. That precedent concerns unauthorized-access law, not Pinterest's own Terms of Service — scraping in a way that violates a platform's ToS is a separate matter of civil contract risk, not a criminal one.

This Actor's output includes personal data where a pin's uploader is an individual — pinner.full_name, username, follower_count, and image_url. If you store or process this data about identifiable people, data protection laws such as the GDPR (EU/UK) or the CCPA (California) may apply to what you do with it, depending on your jurisdiction and use case.

Pinterest Pins, Videos & Search Scraper Plus returns only publicly accessible data. What you do with that data is your responsibility — consult legal counsel for commercial applications involving personal data.

❓ Frequently asked questions

Does Pinterest Pins, Videos & Search Scraper Plus work without a Pinterest account?

Yes. Every request is an unauthenticated, browser-driven request against Pinterest's public pages — no login, cookies, or API token are used or required.

How does Pinterest Pins, Videos & Search Scraper Plus handle Pinterest's anti-scraping measures?

The Actor runs on Playwright, navigating pages like a real browser rather than issuing raw HTTP requests. By default it runs without a proxy; if Pinterest returns an HTTP 403 or 429, it automatically retries the same target through an Apify datacenter proxy, then an Apify residential proxy (retried up to two additional times), escalating only when a block is actually detected.

Can I run Pinterest Pins, Videos & Search Scraper Plus at scale without getting blocked?

maxItems accepts up to 1000 pins per target, and feed targets scroll for up to min(80, max(8, maxItems // 4 + 5)) passes before falling back to deterministic bookmark-cursor paging (up to 40 additional pages) if the target hasn't stalled. No uptime or block-rate figure is published for this Actor; reliability in practice depends on your proxy pool and how aggressively Pinterest is rate-limiting at the time of the run.

How fresh is the data Pinterest Pins, Videos & Search Scraper Plus returns?

Every run fetches live from Pinterest's own pages and feed endpoints at the time it runs — nothing is cached or served from a prior run. scrapedAt on every row records exactly when that row was collected.

Does Pinterest provide an official API I could use instead?

Pinterest publishes a Pinterest API v5 for developers, but it's gated behind an approved developer app and OAuth, and is scoped around managing boards, pins, and content tied to an authenticated business account — not open keyword search or arbitrary public profile/board scraping across other users' content, which is what this Actor does. Building and maintaining your own scraper against Pinterest's internal resource endpoints means re-solving request routing, bookmark-cursor paging, and anti-bot handling yourself.

Which fields work best for AI training and RAG indexing?

For RAG, index description (the natural-language text) alongside pinUrl, board.name, and pinner.username so a retrieval hit can be traced back to its source pin and board. For training data, isVideo, hashtags, totalReactions, and — when includeCounts is on — saveCount form a consistently typed feature set: every field returns as a typed primitive, never a display string that needs parsing.

What happens to personal data returned by this Actor?

Pinterest Pins, Videos & Search Scraper Plus returns only publicly available data, including public pinner identifiers (full_name, username, follower_count, image_url) where a pin's uploader is an individual. The lawful basis for storing and using that data — and compliance with GDPR, CCPA, or other applicable data protection law — sits with you as the operator of the run, not with the Actor.

Does Pinterest Pins, Videos & Search Scraper Plus work with Claude, ChatGPT, and other AI agent tools?

There is no dedicated MCP server documented for this Actor. It is callable as an HTTP endpoint by any agent framework through the Apify API — every response is a flat, typed JSON row, so no HTML-parsing step is required before passing a pin into an LLM's context window.

How does Pinterest Pins, Videos & Search Scraper Plus compare to other Pinterest scrapers?

simpleapi/pinterest-pins-videos-search-scraper and scrapapi/pinterest-pins-videos-search-scraper both document the same output shape — a single image url, a single link_to_video, and an unlabeled reaction_counts object, with no board data or comment counts (observed on the Apify Store, 2026-07-26). scrapapi prices per event, the same model this Actor uses; simpleapi charges a flat monthly price. scrapestorm/pinterest-pins-videos-search-scraper---cheap charges a flat $9.90/month for unlimited keyword-only extraction with a similarly narrow field set — no board data, no comment counts, no pin/board/profile URL routing (observed 2026-07-26). Where this Actor differs from all three: real URL routing to pin/board/profile endpoints, full image-size and video-variant objects, structured board and pinner objects, and explicit save/comment counts as an opt-in field rather than left out of the schema entirely.

ℹ️ Disclaimer

Pinterest Pins, Videos & Search Scraper Plus extracts only publicly available data from Pinterest. This tool is intended for lawful use cases only. Users are responsible for complying with Pinterest's terms of service and applicable data protection laws in their jurisdiction.