Pinterest Search Scraper: Pin Board Details

Pinterest Search Scraper — Extract Pins, Boards and Creator Profiles

Pinterest Search Scraper: Pin Board Details turns one keyword into pins, boards, and creator profiles in a single run, returning fields like pinUrl, boardName, followerCount, and isVerified as structured JSON — no HTML parsing required. It runs logged-out over an Apify Residential proxy and can optionally enrich each creator's bio, website, and follower counts, plus each board's pin and follower counts. Start a run on the Actor page to see live output for any keyword.

What is Pinterest Search Scraper: Pin Board Details?

Pinterest Search Scraper: Pin Board Details is an Apify Actor that expands a single Pinterest keyword search into three entity types — pins, boards, and creator profiles — and returns them as typed, normalized JSON rows. It runs entirely logged-out: no Pinterest account, cookies, or session token are required, only an Apify Residential proxy, which the Actor enforces automatically. It's built for marketers, influencer researchers, and developers or AI engineers who need Pinterest search data as clean JSON rather than scraping HTML themselves.

What Pinterest search and board data is publicly available to scrape?

Pinterest exposes pin, board, and creator search results to any visitor without signing in.

Data Category	Publicly Available	Gated Behind Login
Pin title, description, image, link/domain	Yes	—
Board name, pin count, follower count, cover image	Yes	—
Creator username, bio, followers, verified badge	Yes	—
Keyword search across pins/boards/profiles	Yes	—
Private or "secret" boards	No	Owner's login session
Direct messages, notifications, home feed	No	Login

Pinterest Search Scraper: Pin Board Details only returns publicly visible data — what any visitor sees. Nothing behind a login wall.

What data can I extract with Pinterest Search Scraper: Pin Board Details?

Every row is tagged by resultType (pins, boards, or profiles) so a single "mixed" run can be split back out by entity type.

Field Name	Description
resultType	Which entity this row represents: pins, boards, or profiles
type	Raw Pinterest node type (pin, board, user)
id / node_id	Pinterest's internal ID for the pin, board, or user
title	Pin title, board name, or creator full name/username
username	Creator's Pinterest handle (profile rows)
boardName	Name of the board a pin belongs to (pin rows)
followerCount	Follower count for a board or creator
creatorFollowerCount	Follower count of a pin's creator (pin rows)
pinCount	Number of pins on a board, or a creator's total pin count
boardPinCount	Pin count of the board a pin belongs to (pin rows)
isVerified / creatorIsVerified	Verified-identity flag for a profile or a pin's creator
pinUrl / boardUrl / profileUrl	Direct Pinterest URL to the pin, board, or profile
imageUrl / image_url	Cover image (boards/profiles) or full-size pin image URL
link	Pin's outbound destination URL
domain	Merchant/publisher domain of the pin's destination link
scrapedAt	ISO 8601 UTC timestamp of when the row was collected

Pin fields

node_id, title, description, domain, link, dominant_color, created_at, image_url, image_width, image_height, pinUrl, isVideo, videoUrls, creatorUsername, creatorFullName, creatorFollowerCount, creatorIsVerified, boardName, boardUrl, boardPinCount, boardOwnerUsername, plus the raw board, pinner, reaction_counts, and native_creator objects.

Board fields

id/node_id, name, description, boardUrl, pinCount, followerCount, sectionCount, isCollaborative, ownerUsername, ownerFullName, ownerFollowerCount, imageUrl, enriched.

Creator profile fields

id/node_id, username, fullName, bio, followerCount, followingCount, pinCount, boardCount, isVerified, website, profileUrl, imageUrl, enriched.

🤖 Add-on: Need additional Pinterest data?

If you specifically need shopping-intent pins — pins with a real outbound merchant link, ranked by top merchant domain — pair this Actor with Pinterest Pins Videos Search & Outbound Shopping Links Scraper, which focuses on pin-level outbound-link and domain analytics rather than boards or creator profiles. Use this Actor for the discovery layer (pins + boards + creators) and the outbound-link Actor when merchant-domain ranking is the goal.

How does Pinterest Search Scraper: Pin Board Details differ from the official Pinterest API?

Pinterest's official API requires OAuth 2.0 authorization from a registered app tied to a Pinterest business account, and moving past its Trial tier requires Pinterest's own app review with no guaranteed timeline. This Actor needs neither — it starts from a keyword with no Pinterest account at all.

Feature	Pinterest API	Pinterest Search Scraper: Pin Board Details
Account setup	Business account + registered OAuth app	None — no Pinterest account required
Approval process	App review required to exceed Trial tier	No approval process; runs immediately
Rate limits	Trial: 1,000 requests/day across all endpoints; Standard tier requires approval	Bounded by the maxResults input (up to 10,000 per discovery type per run)
Entities per call	Separate endpoints/resources for pins, boards, and user accounts	Pins, boards, and creator profiles in one run, unified under resultType
Output shape	Per-endpoint JSON, versioned by Pinterest's API schema	Single normalized JSON schema across all three entity types
Credentials to manage	Client ID/secret, access token refresh	None

Use the official API when you already have Pinterest business-account access and only need to manage your own pins and boards. Use this Actor for ad-hoc or bulk keyword research across public pins, boards, and creators without an OAuth setup.

How to use Pinterest Search Scraper: Pin Board Details

This Actor runs on the Apify platform — there's no separate signup or API key beyond an Apify account.

1. Open Pinterest Search Scraper: Pin Board Details on its Apify Store page and click Try for free (or Run).
2. Enter the required searchTerm — e.g. "home office".
3. Optionally set discoveryType (mixed/pins/boards/profiles), contentType, maxResults, and the enrichCreators/enrichBoards toggles.
4. Start the run — Apify Residential proxy is applied automatically.
5. Download results as JSON, CSV, or Excel from the dataset, or pull them via the Apify API.

How to scale to bulk Pinterest search/board extraction

The input schema accepts a single searchTerm string per run — there is no array/bulk-keyword field. To cover multiple keywords, loop: call the Apify API's "Run Actor" endpoint (or the Python/JS client) once per searchTerm, either sequentially or in parallel runs, and merge the resulting datasets afterward. maxResults (up to 10,000) still controls the ceiling per discovery type within each individual run.

What can you do with Pinterest search and board data?

• A content strategist researching visual trends uses title, description, and isVideo from pin rows to see which formats dominate a keyword before planning a content calendar.
• An influencer marketing manager sourcing creators uses followerCount, isVerified, and bio from profile rows to shortlist pinners for outreach without opening each profile.
• A board researcher mapping a niche uses boardName, pinCount, and followerCount from board rows to find the most-followed boards worth monitoring.
• An e-commerce/SEO analyst studying Pinterest search uses domain and link from pin rows to see which destination sites already rank for a keyword.
• An AI engineer building a Pinterest trend-monitoring agent feeds title, description, boardName, and creatorFollowerCount into a RAG index or LLM prompt to summarize what's trending for a keyword without manual scraping.

How does Pinterest Search Scraper: Pin Board Details handle rate limits and blocking?

Apify Residential proxy is enforced in code — even if a caller supplies a different proxyConfiguration, the Actor merges it back to useApifyProxy: true with the RESIDENTIAL group before every request. Each browser context uses a randomized desktop user agent and a stealth init script that hides navigator.webdriver and spoofs plugins/languages to reduce automation fingerprinting. A fresh residential proxy URL is requested for every capture attempt, and each discovery surface (pins/boards/profiles) retries up to 3 times with exponential backoff if no results are collected. If a response comes back with an HTTP 4xx/5xx status or the browser lands on a /login page, the Actor logs a warning and treats that attempt as blocked rather than crashing. If every surface still returns zero rows after all retries, the run finishes cleanly and sets a status message noting that Pinterest may have blocked the session or that the search had no results — it does not fail silently or hang.

⬇️ Input

Parameter	Required	Type	Description	Example Value
searchTerm	Yes	String	Keyword to discover across Pinterest (e.g. home office, sourdough, streetwear).	"home office"
discoveryType	No	String	What to return: mixed (pins+boards+profiles), pins, boards, or profiles. Default: mixed.	"mixed"
maxResults	No	Integer	Cap on results for EACH discovery surface (1–10,000). Default: 10.	10
contentType	No	String	Applies to pins only: all pins or videos only. Ignored for boards/profiles. Default: all.	"all"
enrichCreators	No	Boolean	Fetch each discovered creator's profile page to add bio, follower count, website, verified badge, pin/board counts. Default: true.	true
enrichBoards	No	Boolean	Ensure each discovered board has pin count and follower count. Default: true.	true
proxyConfiguration	No	Object	Proxy configuration; Apify Residential proxy is enforced regardless of input. Default: {"useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"]}.	{"useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"]}

Example input

{
  "searchTerm": "home office",
  "discoveryType": "mixed",
  "maxResults": 10,
  "contentType": "all",
  "enrichCreators": true,
  "enrichBoards": true,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"]
  }
}

⬆️ Output

Results are pushed as typed, normalized JSON rows to the Actor's dataset, with a consistent schema per resultType across runs. Export from the Apify Console as JSON, CSV, Excel, or XML, or fetch via the Apify API/client. Billing is pay-per-event: each row pushed to the dataset (pin, board, or profile) is charged as one row_result event.

Example output

Pin row

{
  "query": "home office",
  "node_id": "1093458667405922341",
  "type": "pin",
  "title": "Minimalist Home Office Setup",
  "description": "Clean desk layout with natural light and walnut accents",
  "domain": "example-blog.com",
  "link": "https://example-blog.com/home-office-ideas",
  "dominant_color": "#e8e2d8",
  "created_at": "Tue, 15 Jul 2025 12:51:39 +0000",
  "board": { "id": "140874927373222", "name": "Home Office Ideas", "pin_count": 142 },
  "reaction_counts": { "1": 12, "2": 3 },
  "native_creator": {},
  "pinner": { "username": "ellysebull", "full_name": "Ellyse Bull", "follower_count": 8342 },
  "image_url": "https://i.pinimg.com/originals/aa/bb/cc/aabbcc.jpg",
  "image_width": 1000,
  "image_height": 1500,
  "resultType": "pins",
  "pinUrl": "https://www.pinterest.com/pin/1093458667405922341/",
  "isVideo": false,
  "videoUrls": [],
  "creatorUsername": "ellysebull",
  "creatorFullName": "Ellyse Bull",
  "creatorFollowerCount": 8342,
  "creatorIsVerified": false,
  "boardName": "Home Office Ideas",
  "boardUrl": "https://www.pinterest.com/ellysebull/home-office-ideas/",
  "boardPinCount": 142,
  "boardOwnerUsername": "ellysebull",
  "scrapedAt": "2026-07-25T09:12:41Z"
}

Board row

{
  "resultType": "boards",
  "type": "board",
  "query": "home office",
  "node_id": "140874927373222",
  "id": "140874927373222",
  "name": "Home Office Ideas",
  "title": "Home Office Ideas",
  "description": "Modern home office inspiration and desk setups",
  "boardUrl": "https://www.pinterest.com/ellysebull/home-office-ideas/",
  "pinCount": 142,
  "followerCount": 4210,
  "sectionCount": 6,
  "isCollaborative": false,
  "ownerUsername": "ellysebull",
  "ownerFullName": "Ellyse Bull",
  "ownerFollowerCount": 8342,
  "imageUrl": "https://i.pinimg.com/474x/aa/bb/cc/aabbcc.jpg",
  "scrapedAt": "2026-07-25T09:12:41Z",
  "enriched": true
}

Creator profile row

{
  "resultType": "profiles",
  "type": "user",
  "query": "home office",
  "node_id": "140943646788322",
  "id": "140943646788322",
  "username": "ellysebull",
  "profileUrl": "https://www.pinterest.com/ellysebull/",
  "fullName": "Ellyse Bull",
  "title": "Ellyse Bull",
  "bio": "Interior designer sharing home office & workspace ideas",
  "followerCount": 8342,
  "followingCount": 512,
  "pinCount": 980,
  "boardCount": 24,
  "isVerified": false,
  "website": "https://ellysebulldesign.com",
  "imageUrl": "https://i.pinimg.com/280x280_RS/aa/bb/cc.jpg",
  "scrapedAt": "2026-07-25T09:12:41Z",
  "enriched": true
}

Values that are genuinely unavailable are returned as null rather than a faked 0 or empty string.

How does it work?

Pinterest Search Scraper: Pin Board Details drives a real headless Chromium browser (Playwright) to the Pinterest search surface matching the requested discoveryType — /search/pins/, /search/boards/, or /search/users/ — routed through an Apify Residential proxy. Rather than parsing rendered HTML, it listens for Pinterest's own internal BaseSearchResource network responses and reads structured result nodes directly out of that JSON. It paginates by scrolling the page and, once available, by replaying the same internal resource call with Pinterest's bookmark/cursor token until maxResults is reached or results run out. Optional enrichment issues one extra request per discovered creator or board to fill in fields the search response omits. Because the Actor reads Pinterest's own data resource rather than CSS selectors, the output schema stays stable even when Pinterest's visual layout changes, and only publicly visible data is ever returned.

Integrations

Pinterest Search Scraper: Pin Board Details runs on Apify, so it works with any tool that can call the Apify API — no Pinterest-specific integration is required.

Calling Pinterest Search Scraper: Pin Board Details programmatically

from apify_client import ApifyClient

client = ApifyClient("<APIFY_API_TOKEN>")
run = client.actor("scraper-engine/pinterest-search-scraper-pin-board-details").call(
    run_input={
        "searchTerm": "home office",
        "discoveryType": "mixed",
        "maxResults": 10,
    }
)
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["resultType"], item.get("title"))

Works in Go, Ruby, Node.js, cURL — any language that can make an HTTP request.

MCP integration for AI agents

This Actor is reachable through Apify's official MCP server. Register it with npx @apify/actors-mcp-server (with APIFY_TOKEN set) and pass --actors=scraper-engine/pinterest-search-scraper-pin-board-details to expose it as a callable tool. Compatible with Claude Desktop, Claude Code, and other MCP-compliant clients.

No-code tools (n8n, Make, LangChain)

In n8n, use the Apify node (or an HTTP Request node pointed at the Actor's run endpoint) to trigger a run and read back the dataset. In Make, use Apify's dedicated app module to run the Actor and retrieve dataset items into a scenario. In LangChain, install langchain-apify and use ApifyActorsTool or ApifyWrapper to run the Actor and load its dataset directly into a chain or agent.

Is it legal to scrape Pinterest search results and boards?

Scraping publicly available Pinterest data — pins, boards, and creator profile information visible to any signed-out visitor — is generally permitted in most jurisdictions. Pinterest Search Scraper: Pin Board Details returns only that publicly visible data; it never accesses private/secret boards, DMs, or anything behind a login wall. Because creator profile rows contain personal data (username, bio, follower counts tied to an identifiable person), storing or reusing that data may fall under GDPR, CCPA, or similar personal-data regimes depending on your jurisdiction and use case. Consult legal counsel if your use case involves bulk storage of personal data.

Frequently asked questions

What Pinterest fields does Pinterest Search Scraper: Pin Board Details return?

It returns resultType, title, pinUrl/boardUrl/profileUrl, followerCount, and isVerified as its core fields, plus dozens more specific to pins, boards, and profiles — see the data fields section above.

Does Pinterest Search Scraper: Pin Board Details require a Pinterest account or login?

No. It runs fully logged-out; the only credential it needs is an Apify Residential proxy, which is enforced automatically.

How many pins, boards, and profiles can I extract in one run?

Up to maxResults (max 10,000) per discovery surface. With discoveryType: "mixed", that cap applies independently to pins, boards, and profiles in the same run.

What happens if a search returns zero results?

The run still completes without erroring. If a surface collects nothing after 3 retries, the Actor logs a warning for that surface and moves on; if every surface ends up empty, it sets a run status message noting the search may have no results or the session was blocked.

Can I scrape multiple Pinterest search terms at once?

Not within a single run — searchTerm accepts one keyword. To cover multiple keywords, trigger one run per term via the Apify API (sequentially or in parallel) and merge the resulting datasets.

Does Pinterest Search Scraper: Pin Board Details work with Claude, ChatGPT, and other AI agent tools?

Yes. It's reachable through Apify's MCP server (npx @apify/actors-mcp-server --actors=scraper-engine/pinterest-search-scraper-pin-board-details) for MCP clients like Claude Desktop, and callable as a standard HTTP/API endpoint by any other agent framework.

How does Pinterest Search Scraper: Pin Board Details compare to other Pinterest scrapers?

Most Pinterest scrapers return a single entity type, typically pins. This Actor's discoveryType input covers pins, boards, and creator profiles from one keyword in one run, with optional enrichment fetches for creator and board details — differences you can verify directly against the input schema and dataset views.

Does Pinterest Search Scraper: Pin Board Details return data in a format LLMs can use directly?

Yes. Output is typed, normalized JSON with consistent field names across runs and entity types — no HTML parsing or CSS selectors needed. Pass it directly to an LLM prompt, index it into a vector store, or feed it to an agent tool.

What happens when Pinterest changes its layout or anti-bot system?

The Actor reads Pinterest's internal BaseSearchResource JSON rather than the rendered page layout, and the Actor is maintained to keep the output schema stable as Pinterest changes. No specific update turnaround time is published.

Can I use Pinterest Search Scraper: Pin Board Details without managing proxies or browser infrastructure?

Yes. The Actor runs its own headless Chromium browser via Playwright and enforces Apify Residential proxy rotation internally — you don't configure or maintain either.

Which fields work best for AI training data and RAG indexing?

For RAG, index the high-information text fields: title, description, bio. For structured training features, followerCount, pinCount, boardCount, and isVerified return as consistent typed primitives (numbers/booleans) across every row.

Related scrapers

Scraper Name	What it extracts
Pinterest Pins Videos Search & Outbound Shopping Links Scraper	Pinterest pins with outbound merchant link, domain, and shopping-pin flags
Instagram Profile Scraper	Instagram profile bio, followers, and post metadata
TikTok Trending Videos Scraper With Author Profile	TikTok trending videos plus the posting creator's profile data
Twitter/X Profile Scraper	Twitter/X profile bio, follower counts, and account metadata
Facebook User Search Scraper: Photos & AI Bio Analysis	Facebook user search results with photos and AI-analyzed bio data

Your feedback

Found a bug or missing a field in Pinterest Search Scraper: Pin Board Details? Let us know through the Issues tab on the Actor's Apify Console page so we can take a look. Feedback helps keep the schema accurate as Pinterest's site evolves.