![Pinterest [Only $1.9💰] PIN | Ideas | Profile | Board | Scraper avatar](https://images.apifyusercontent.com/Em7dwBnut_J-ghcZR1fGjKoAVdb2tznSAZyLMUHxWt0/rs:fill:250:250/cb:1/aHR0cHM6Ly9hcGlmeS1pbWFnZS11cGxvYWRzLXByb2QuczMudXMtZWFzdC0xLmFtYXpvbmF3cy5jb20vbmduOHZSRVNUa3NleVdFNnAtYWN0b3ItM25jYjNJZ1FKWmtFUnZQSVUtbWVWTHdIclpmTC1waW50ZXJlc3QucG5n.webp){kind=avatar}
Pinterest [Only $1.9💰] PIN | Ideas | Profile | Board | Scraper
Pricing
from $1.90 / 1,000 results
Go to Apify Store
Example
Pinterest [Only $1.9💰] PIN | Ideas | Profile | Board | Scraper
[Only $1.9💰] Scrape Pinterest pins, boards, profiles and search into JSON or CSV. Titles, descriptions, images/video, creator and board info, links, engagement. Optional comments and profile fields. URLs or keywords. Great for trend research, content planning and creator discovery.
Pricing
from $1.90 / 1,000 results
Rating
0.0
(0)
Developer
Muhamed Didovic
Maintained by Community
Actor stats
0
Bookmarked
2
Total users
1
Monthly active users
7 days ago
Last modified
Categories
Share
Pinterest Scraper
Unlock Pinterest pin data at scale — scrape pins from search, profiles, boards, ideas hubs, and direct pin URLs using the same JSON resources the Pinterest web app uses. Optional flattened rows for spreadsheets, plus comments and profile enrichment when you need full context.
"From search grids and idea hubs to board feeds and individual pins — turn Pinterest browsing into structured datasets."
How it works
Overview
The Pinterest Scraper is built for marketers, researchers, and analysts who need public pin metadata (images, engagement, board context, SEO fields, and more). It runs on the Apify platform with Crawlee and Cheerio, supports residential proxies, and exports to JSON or CSV (flattened mode is ideal for CSV).
What does Pinterest Scraper do?
The Pinterest Scraper enables you to:
Comprehensive data collection
- Pins
- Collect pin ids, canonical URLs, repin counts, reaction counts, and aggregated stats where available
- Image variants (multiple sizes) and dominant color
- Board context (name, privacy, owner) when the listing provides it
- Rich listing fields merged with PinResource detail where applicable
- Comments (optional)
- Per-pin comments via Pinterest's UnifiedCommentsResource (when enabled)
- User profile enrichment (optional)
- Public UserResource fields merged into pinner, owner, and related user blobs (e.g. follower_count, avatars)
Advanced crawling
- Pagination: Search, user activity, board feeds, and ideas hub feeds paginate until max items or no more bookmarks
- Concurrency & retries: Configurable max/min concurrency and max request retries
- Proxy-friendly: Residential proxy groups recommended for stable access
Flexible start points
See Supported start URLs for every accepted pattern and a copy-paste startUrls example covering ideas hub, pin, profile, search, and board. In short: pin URLs, search URLs (/search/pins, /search/videos, …), profile (/{user}/), board (/{user}/{board}/), ideas hub (/ideas/slug/id/), or Search queries without pasting URLs.
This tool is ideal for:
- Trend and visual research
- Competitive inspiration tracking
- Building labeled image / metadata corpora from public pins
- Enriching pin lists with comments and creator stats
Features
- Multiple entry types: Search, profile, board, ideas hub, and direct pin URLs in one run
- Keyword mode: Search queries (multi-line) + Search type (
pins,videos,boards,users) when you prefer not to paste full URLs - Optional comments: Toggle Include comments for a comments field (nested object when not flattened; dot keys when flattened)
- Optional user enrichment: Toggle Include only user info to merge UserResource into pin-related users
- Flattened output: One level of keys with dot notation — best for Excel/CSV pipelines
- Search page cap: List end page limits how many search API pages to walk (omit for no cap, still bounded by max items)
- Structured export: Dataset items as JSON; CSV export reflects the same flat/nested shape you choose
How to use
- Apify: Open the actor and sign in if needed.
- Start URLs or Search queries: Paste one or more Pinterest URLs, or leave URLs empty and fill Search queries (and Search type).
- Options: Set max items, flattened output, include comments, include only user info, list end page (optional), concurrency, retries, and proxy (residential recommended).
- Run: Start the actor; results appear in the default dataset.
Supported start URLs
Use full HTTPS URLs on pinterest.com or *.pinterest.com (e.g. www.pinterest.com, br.pinterest.com). Query strings are kept where Pinterest uses them (e.g. ?q= on search).
| Kind | Path pattern | Notes |
|---|---|---|
| Pin | /pin/{id} or /pin/{slug}--{id} | Numeric id, or slug ending with --{id}. |
| Search | /search/{vertical}/… | vertical must be pins, videos, boards, or users. Example: /search/pins/?q=nails. |
| Ideas hub | /ideas/{topic-slug}/{numeric-id}/ | Exactly three path segments; last segment digits only. Example: /ideas/beauty/935541271955/. |
| Board | /{username}/{board-slug}/ | Exactly two segments. Not profile tabs (e.g. …/user/pins/ is reserved, not a board). |
| Profile | /{username}/ | Exactly one segment; username must not be a reserved first segment (search, pin, ideas, today, …). |
Without start URLs: set Search queries (and Search type). The actor opens https://www.pinterest.com/search/{searchScope}/?q=… per query (searchScope: pins | videos | boards | users). Legacy Search keyword is one such query.
Example startUrls (what we support)
You can use one of these or mix several in a single run. Maximum number of items is a shared cap across every start URL (pins are merged into one dataset).
| Entry type | Example URL |
|---|---|
| Ideas hub | https://www.pinterest.com/ideas/beauty/935541271955/ |
Pin (numeric id or slug--id) | https://www.pinterest.com/pin/1829656094716568/ or https://www.pinterest.com/pin/uitas--1829656094716568/ |
| Profile | https://www.pinterest.com/dudadelsanto/ |
| Search | https://www.pinterest.com/search/pins/?q=nail+art&rs=hub_page |
| Board | https://www.pinterest.com/dudadelsanto/nail-inspo/ |
Copy-paste as your Start URLs list:
Not supported: pin.it / other short domains, board section URLs (…/board/section/), non-/ideas/ three-segment paths, and hosts outside *.pinterest.com.
Input configuration
See Example startUrls (what we support) for a copy-paste list with every entry type (ideas hub, pin, profile, search, board).
Example input (single pin URL + all optional enrichments + flattened rows):
Keyword-only example (same max items budget shared across queries):
Input fields
| Field | Description |
|---|---|
startUrls | String list: board, profile, ideas hub, search, or pin URLs (www or country subdomain on *.pinterest.com). |
searchQueries | When startUrls is empty, one Pinterest search per non-empty line (uses searchScope). |
searchScope | pins (default), videos, boards, or users — only affects keyword-built search URLs. |
searchKeyword | Legacy single term; same as one entry in searchQueries. |
maxItems | Maximum pins to collect (default 100; free users may be capped by the actor). |
maxSearchPages | Max search API pages (optional); omit or ≤0 for no page limit. |
flattenedOutput | If true, one object per pin with dot-separated keys (CSV-friendly). |
includeComments | Fetch comments per pin (UnifiedCommentsResource). |
includeOnlyUserInfo | Merge UserResource into pinner/owner (and related users). |
maxConcurrency / minConcurrency | Crawler concurrency. |
maxRequestRetries | Retries per failed request. |
proxy | Apify proxy configuration (residential recommended). |
Output structure
Each dataset item is one pin (merged listing + detail). The exact keys depend on flattened output and on which toggles were enabled.
More samples below show the same pin row shape from different starts. With flattened output off, fields are nested objects/arrays instead of dot keys.
Sample JSON — pin row, flattened, comments + user info
The example below is the first record from a real run with Flattened output, Include comments, and Include only user info enabled (same as data_pin.json in the repository). Keys use dot notation; comment threads use comments.0.*, comments.1.*, …
Sample JSON — ideas hub (Beauty category), flattened
Start URL: https://www.pinterest.com/ideas/beauty/935541271955/. Each dataset item is still a pin ("type": "pin"); the ideas hub feed supplies listing fields, then the same pin pipeline applies (optional comments / user enrichment). First record from data_ideas_beauty.json.
Reading these samples
type: Always"pin"for pin dataset rows (search, profile, board, ideas hub, or direct pin URL).id,url: Pin id and canonical pin URL.pinner.*,owner.*,board.owner.*,native_creator.*,via_pinner.*,closeup_attribution.*, etc.: User-shaped fields; with Include only user info, profile fields such asfollower_countare filled where the API returns them.comments.N.*: Present when Include comments is on —content,name, profileurl,created_at, counts, optionalavatar.aggregated_pin_data.*: Aggregated pin node (saves, comment_count at aggregated level, etc.).images.*: Multiple image size buckets (60x60,236x,orig, …).- Ideas / listing-only fields: Some grids expose extra keys (e.g.
seo_url,like_count) that may be absent on rows from a bare pin URL; presence varies by source and Pinterest’s payload.
With flattened output off, the same data is stored as nested JSON (objects and arrays) instead of dot keys.
Output fields (flattened pin rows — high level)
This section applies to both flattened samples above (direct pin + ideas hub). Pinterest may add or omit fields over time; treat unknown keys as optional.
Pin core
node_id,id: Internal / numeric identifiers.type:"pin".url: Full HTTPS URL of the pin.title,description,closeup_unified_description,seo_title,seo_description: Text and SEO-oriented fields (may be empty).created_at: Pin creation timestamp string from Pinterest.repin_count,share_count,comment_count,reaction_counts.*: Engagement metrics where exposed on the listing.image_medium_url,image_signature,dominant_color: Visual metadata.images.<size>.width,images.<size>.height,images.<size>.url: Per-size image assets.
Aggregated pin data
aggregated_pin_data.id,aggregated_pin_data.node_id: Aggregated node identifiers (used for comments API).aggregated_pin_data.aggregated_stats.*: e.g. saves / done counts.aggregated_pin_data.comment_count: Comment count on the aggregated node (may differ from listingcomment_count).aggregated_pin_data.did_it_data.*: “Tried it” style engagement breakdown when present.
Board
board.id,board.name,board.url,board.privacy: Board identity and visibility.board.pin_thumbnail_urls.N: Sample thumbnails from the board.board.owner.*: Board owner user fields (enriched when user info is enabled).
Users (pinner, owner, attribution, etc.)
Flattened keys share the same suffixes: *.username, *.full_name, *.id, *.image_small_url, *.follower_count, *.indexed, etc., under prefixes like pinner, owner, closeup_unified_attribution, native_creator, via_pinner.
Comments (when enabled)
comments.N.id: Comment id.comments.N.content: Text body.comments.N.name: Commenter display/username-style label.comments.N.url: Commenter profile URL on Pinterest.comments.N.created_at: Timestamp when provided.comments.N.like_count,reply_count,helpful_count: Interaction counts.comments.N.avatar: Present for some commenters.
Other
pin_join.visual_annotation.N: Topic-style labels.pin_join.annotations_with_links.<label>.url/.name: Linked idea hubs.privacy,is_repin,comments_disabled,is_hidden: Flags and moderation-related fields.pinner_follower_count: Convenience duplicate of pinner follower count when enrichment is on.
Explore more scrapers
If this actor is useful, see more tools at memo23's Apify profile.
Support
- For issues or feature requests, use the Issues tab on this actor in the Apify Console.
- Contact:
- Website: https://muhamed-didovic.github.io/
- Email: muhamed.didovic@gmail.com
Additional services
- Customization or full dataset delivery: muhamed.didovic@gmail.com
- API-style usage questions: muhamed.didovic@gmail.com
