Pinterest Scraper — Pins, Boards & Keyword Search

Pinterest Scraper lets you scrape Pinterest pins by keyword search, board URL, or username — no official Pinterest API key, no login required. It targets the in.pinterest.com/resource/* internal API endpoints that return clean JSON (HTTP 200) instead of the bot-blocked www.pinterest.com HTML frontend that returns 403 to scrapers. Every result includes a parse_confidence score so you know your data is clean. Pay only per pin collected.

Why This Pinterest Scraper Beats @maximedupre/pinterest-keyword-scraper

Feature	This actor	@maximedupre
Scrape modes	keywords + boards + usernames	keywords only
Endpoint	in.pinterest.com resource API (JSON, always 200)	www.pinterest.com HTML (frequent 403)
Output fields	23 fields incl. repin count, dominant color, pinner	~8 fields
Parser health signal	parse_confidence + warnings in every record	None
Proxy	Configurable residential (buyer-paid)	Fixed

What Pinterest Data You Get

Each pin record includes 23 fields:

Field	Description
id	Pinterest pin ID
pin_url	Canonical pin URL (https://www.pinterest.com/pin/{id}/)
title	Pin title or grid title
description	Pin description (falls back to alt text)
alt_text	Auto-generated or manual alt text
image_url	Largest available image (736px or original)
image_url_236x	Thumbnail image (236px)
dominant_color	Hex dominant color of the pin image
repin_count	Number of saves/repins
link	External URL the pin points to
domain	Domain of the external link
pinner_id	Numeric pinner (user) ID
pinner_username	Pinner username
pinner_full_name	Pinner display name
board_id	Numeric board ID
board_name	Board display name
board_url	Full board URL
created_at	Pin creation time (ISO-8601 UTC)
source_mode	"search" / "board" / "user_boards"
parse_confidence	0–1 parse quality score (1.0 = perfect)
warnings	List of quality warning codes (empty = clean)
scraped_at	Batch scrape timestamp (ISO-8601 UTC)

Pinterest Scraper Use Cases

• Content research — discover trending Pinterest pins for any niche by keyword
• Competitor analysis — scrape a competitor's Pinterest boards to see their pinning strategy
• Influencer monitoring — bulk-export a creator's full Pinterest presence by username
• E-commerce product research — find product pins with external links for affiliate/market research
• Image dataset collection — harvest labeled images with dominant color metadata for ML

How to Use the Pinterest Scraper

Scrape Pinterest by Keyword (content & trend research)

{
  "keywords": ["minimalist home office", "sustainable fashion"],
  "maxItems": 200,
  "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }
}

Scrape Pinterest Board by URL (archive or monitor a specific board)

{
  "boardUrls": [
    "https://www.pinterest.com/user/my-board/",
    "https://www.pinterest.com/anotheruser/products/"
  ],
  "maxItems": 500
}

Scrape Pinterest User Profile (full account export)

{
  "usernames": ["somedesigner", "@anotheraccount"],
  "maxItems": 100
}

Mixed — all three Pinterest scrape modes in one run

{
  "keywords": ["bohemian decor"],
  "boardUrls": ["https://www.pinterest.com/user/board/"],
  "usernames": ["targetuser"],
  "maxItems": 100
}

Pricing — Pay Per Pinterest Pin

This actor uses pay-per-result pricing: $5.00 per 1,000 pins (PPE — pay per result, no per-run fees). You are charged only for pins successfully scraped and returned in your dataset. Scraping 500 pins costs ~$2.50. Most runs (100–200 pins) cost less than $1.

How Pinterest Scraper Reliability Works

• Targets in.pinterest.com/resource/* endpoints — not the HTML frontend that blocks scrapers
• Lightweight HTTP requests without Playwright overhead
• parse_confidence and warnings fields in every record provide machine-readable parser health signals
• Residential proxy strongly recommended; proxy cost billed to your Apify account at standard rates

Frequently Asked Questions

Does this scraper need a Pinterest login? No. The in.pinterest.com resource endpoints return public pin data without authentication.

What proxy should I use? Residential proxy is strongly recommended. Pinterest aggressively blocks datacenter IPs. Configure proxyConfiguration with RESIDENTIAL group.

Can I scrape private Pinterest boards? No. Private boards require Pinterest login, which is not supported. Only public pins are accessible.

What does maxItems do in username mode? In username mode, the maxItems limit applies per board, not per user total. A user with 10 boards at maxItems=50 can return up to 500 pins.

What is repin_count? Extracted from aggregated_pin_data.aggregated_stats.saves. May be null for newly created pins.

---

Not affiliated with Pinterest. Data retrieved from publicly accessible Pinterest endpoints.

Integrations

Built for social-media marketers and visual-content researchers pulling pins, boards, and keywords for trend and audience analysis — the JSON/dataset output drops into the tools you already run, no glue code:

• n8n / Make / Zapier — trigger a run or pipe every new dataset item into 500+ apps (Google Sheets, Airtable, Slack, HubSpot, your database) with no code: n8n, Make, Zapier.
• Webhooks — fire your own endpoint the moment a run finishes, to push results straight into your pipeline (docs).
• MCP server — expose this actor as a tool to Claude, Cursor, or any MCP client so an AI agent can pull this data mid-conversation (guide).
• API & SDKs — fetch the dataset as JSON, CSV, or Excel through the Apify REST API or the Python / JS SDKs.

See all Apify integrations.

More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

• Reddit Scraper
• Social Media Finder
• Telegram Channel Scraper
• Truth Social Scraper
• Twitch Scraper
• Douyin Scraper

Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.