Pinterest Board Pins Scraper
Pricing
from $1.00 / 1,000 results
Pinterest Board Pins Scraper
Collect public pins from Pinterest boards and board sections. Export individual pin records with media, source links and board context using cursor pagination.
Pricing
from $1.00 / 1,000 results
Rating
0.0
(0)
Developer
ScrapingMonkey
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
5 days ago
Last modified
Categories
Share
Export public pins from a Pinterest board or a selected board section with one pin per dataset row. Pinterest Board Pins Scraper collects descriptions, images, available video links, source websites and creator details while preserving the collection context.
Start from a thematic board you already know and build a reusable content inventory. Board and section URLs use the same result schema, so the output remains consistent across different collection sizes.
| At a glance | Details |
|---|---|
| 📥 Input | Enter full Pinterest board URLs (/username/board/) or section URLs (/username/board/section/). A section URL collects only that section. |
| 📤 Output | One pin per success row with the input source retained |
| 📄 Pagination | Result pages per input; page sizes and availability are controlled by Pinterest |
| 🔐 Login required | No |
| ⚡ Processing | Up to 5 HTTP requests concurrently; up to 5 attempts for temporary failures |
| 💾 Delivery | One Apify dataset view with individual records and complete nested JSON |
What the Pinterest board pins scraper collects 🗂️
The Actor resolves the board or section and paginates its public pins. A board starts with its main feed. When that feed ends, sections can be collected within the remaining total page budget; repeated pin IDs are removed within that input.
Data can include:
- Pin IDs, canonical links, text and images
- Available video variants, source websites and domains
- Creator and board metadata exposed with each pin
- Source board or section context for grouping exported rows
- Visible pin counters and optional rich metadata
How to collect board pins from Pinterest 🚀
- Enter one or more supported inputs.
- Set the page budget and any collection option you need.
- Start the Actor.
- Open the Pins dataset view and review success or failed rows.
- Export the dataset or retrieve records from your application.
pagesPerBoard is one total pin-page budget per input, shared by the main feed and sections. The main feed is collected first; includeSections=true continues into sections only after that feed ends and budget remains. Metadata and section-list requests do not count as pin pages. A direct section URL collects only that section.
Pinterest board pins output fields 📦
| Field | Type | Meaning |
|---|---|---|
input | string | Original submitted input. |
status | string | Whether this entity was successfully collected. |
page | integer or null | One-based page within this input's collection. |
source_board | object or null | Board requested as the source. |
source_section | object or null | Board section requested as the source, when applicable. |
id | string or null | Id when supplied by Pinterest. |
url | string or null | Url when supplied by Pinterest. |
title | string or null | Title when supplied by Pinterest. |
description | string or null | Description when supplied by Pinterest. |
created_at | string or null | Created at when supplied by Pinterest. |
link | string or null | Link when supplied by Pinterest. |
domain | string or null | Domain when supplied by Pinterest. |
alt_text | string or null | Alt text when supplied by Pinterest. |
auto_alt_text | string or null | Auto alt text when supplied by Pinterest. |
seo_title | string or null | Seo title when supplied by Pinterest. |
seo_description | string or null | Seo description when supplied by Pinterest. |
seo_alt_text | string or null | Seo alt text when supplied by Pinterest. |
dominant_color | string or null | Dominant color when supplied by Pinterest. |
image_url | string or null | Image url when supplied by Pinterest. |
images | array or null | Available image variants, preserved in one dataset cell. |
videos | array or null | Available video variants with duration in milliseconds, preserved in one dataset cell. |
has_video | boolean or null | Whether video variants were present in this response. |
is_video_raw | boolean or null | Raw Pinterest is_video flag; video variants can exist when it is false. |
is_repin | boolean or null | Is repin when supplied by Pinterest. |
is_promoted | boolean or null | Is promoted when supplied by Pinterest. |
repin_count | integer or null | Repin count reported for this pin; separate from aggregate saves. |
comment_count | integer or null | Comment count reported for this individual pin. |
favorite_user_count | integer or null | Favorite user count when supplied by Pinterest. |
share_count | integer or null | Share count when supplied by Pinterest. |
comments_disabled | boolean or null | Comments disabled when supplied by Pinterest. |
aggregated_pin_id | string or null | Pinterest aggregate ID shared by related copies of the pin. |
aggregated_comment_count | integer or null | Comment count reported for the aggregated pin. |
aggregated_save_count | integer or null | Save count reported for the aggregated pin. |
aggregated_done_count | integer or null | Tried-it count reported for the aggregated pin. |
reactions | array or null | Reactions when supplied by Pinterest. |
author | object or null | Author when supplied by Pinterest. |
board | object or null | Board when supplied by Pinterest. |
section | object or null | Section when supplied by Pinterest. |
product | object or null | Product fields when product metadata exists. Raw zero prices do not establish a free product. |
Nested field structure:
source_board:id,url,name,description,pin_count,follower_count,section_count,sectionless_pin_count,collaborator_count,is_collaborative,privacy,category,cover_image_url,cover_image_hd_url,last_modified_at,owner,images.source_board.owner:id,username,name,url,image_url,image_large_url,is_verified,is_verified_merchant,is_private,follower_count.source_board.images[]:variant,url,width,height,dominant_color.source_section:id,title,slug,description,pin_count,url.images[]:variant,url,width,height,dominant_color.videos[]:variant,url,width,height,duration_ms,thumbnail_url.reactions[]:type,count.author:id,username,name,url,image_url,image_large_url,is_verified,is_verified_merchant,is_private,follower_count.board:id,url,name,description,pin_count,follower_count,section_count,sectionless_pin_count,collaborator_count,is_collaborative,privacy,category,cover_image_url,cover_image_hd_url,last_modified_at,owner,images.board.owner:id,username,name,url,image_url,image_large_url,is_verified,is_verified_merchant,is_private,follower_count.board.images[]:variant,url,width,height,dominant_color.section:id,title,slug,description,pin_count,url.product:metadata_id,price_value_raw,price_currency,availability,is_out_of_stock,is_stale.
The examples below use normalized public response data. Values are snapshots and may change; every top-level output field is included. Different media variants and nested objects remain inside the same row.
Complete representative success result:
Complete section result:
Complete failed dataset item:
A failed row preserves input, sets status to failed, and sets every other top-level field to null. The reason is written to the run log. Optional successful values remain null or empty when Pinterest omits them. The single dataset view exposes object fields as useful columns; arrays are kept in their parent row rather than expanded into additional rows or views.
Input and pagination settings ⚙️
| Parameter | Type | Required | Default | Rules |
|---|---|---|---|---|
inputList | array of strings | Yes | None | Enter full Pinterest board URLs (/username/board/) or section URLs (/username/board/section/). A section URL collects only that section. |
pagesPerBoard | integer | No | 1 | Total pin-page budget per board or section input. A board starts with its main feed, then visits sections if that feed ends and budget remains. Section listing requests do not count as pin pages. Minimum 1. |
includeSections | boolean | No | true | After the main board feed ends, collect its sections using the remaining total page budget. Ignored for a direct section URL. No section requests are made after the page budget is exhausted. |
Use a supported board URL such as https://www.pinterest.com/luizacordery/fits/ or a section URL such as https://www.pinterest.com/luizacordery/fits/doll-outfit-inspo/. A profile URL or a pin URL is not a board input.
Use canonical HTTPS links on www.pinterest.com or pinterest.com. Country-specific hosts, shortened pin.it links and unsupported paths are not accepted.
Duplicate normalized inputs are processed once. A returned identifier is deduplicated within the pagination of one source input; the same object found under different source inputs retains each source relationship.
The first result request counts as page 1. Source validation and preparation requests do not consume result pages. A short or filtered page can continue if it supplies a usable cursor. Collection stops at the page budget or the end of pagination; a repeated cursor does not trigger an endless loop.
Pinterest board pins use cases 🎯
Thematic board exports
Collect a curated board and review its pin descriptions, media and external sources. Use the export as a traceable starting point for topic research.
Section-focused reference lists
Use a section URL to narrow collection to a particular subtopic. Keep the source section when combining several exports.
Repeated collection snapshots
Run the same board inputs on a schedule and compare returned IDs or metadata in your own system. Changes in a limited sample do not prove content was deleted.
Pricing and saved-result behavior 💰
Check the Actor’s Pricing tab for the active charging model and current rate. Store settings may change, so this README does not state an unverified fixed price or runtime.
Under dataset-item pricing:
- Each unique success result represents one pin for its source input.
- An invalid or unavailable input, an input with no accessible results, or a request that exhausts retries can produce a
failedrow. - Retry attempts and supporting metadata requests do not create extra dataset rows by themselves.
- Nested media, author and source fields stay inside their parent result.
- A normal empty continuation after earlier successes creates no additional result row.
- Saved failed rows are not assumed to be free. Check the active pricing configuration for their treatment.
Larger page budgets and more inputs can produce more saved rows. Start with a small run and check actual usage before increasing the workload.
Pinterest board pins API 🔌
Replace $ACTOR_ID with the identifier shown in this Actor’s API tab and $APIFY_TOKEN with your Apify token.
Download JSON, CSV, Excel, XML or other formats available in the Console, or retrieve the dataset through the Apify API. Schedules, webhooks and Apify integrations can connect results to Google Sheets, Make, Zapier, n8n, cloud storage or your own backend. These are connection options rather than integrations already configured by the Actor.
Reliability, retries, and public-data limits ⚠️
Collection uses pure HTTP with up to five concurrent requests. Invalid syntax and confirmed missing, removed or inaccessible targets stop without unnecessary retries. Temporary network or proxy failures, timeouts, blocking responses, malformed data, throttling and server errors are retried up to five total attempts per request.
Earlier successful pages remain saved when a later request fails. A normal end after previously saved results is not retried. An input that produces no accessible results can receive a failed row; this does not by itself prove the underlying account or collection does not exist. A later exhausted request can append a failed row while keeping earlier output.
Pinterest controls public availability, ranking, fields and pagination. Private, deleted, restricted or otherwise unavailable data can be omitted. Counts can change during collection, and media links can expire. Successful HTTP research confirms the supported request paths and pagination on tested sources, rather than future availability or exhaustive coverage.
A selected page budget yields a sample, not a promise to match the board’s reported pin count. Pins can appear in multiple source responses; duplicates are removed within one input. A board’s reported totals can include unavailable content and can change during the run.
An invalid string within a valid input list does not stop other inputs. A configuration that fails validation, such as a non-string list item or an invalid page-count type, exits before requests start. Infrastructure errors such as startup failure, unavailable dataset storage or an unrecoverable result-save error can stop the whole run. A failed dataset save is not retried as a new scraping request.
Frequently asked questions ❓
Can I collect just one board section?
Yes. Submit the section’s full URL. Its pins use the same output schema as board pins.
Does a board run include sections?
With includeSections=true, it continues into sections after the main feed ends and while the total pagesPerBoard budget remains. A small budget on a large board can be used entirely by the main feed.
Does it return board information as separate rows?
No. The output remains one row per pin, with source context attached. Supporting metadata and section discovery do not create extra dataset tables.
Does it require Pinterest login or personal cookies?
No. The Actor uses HTTP requests from the public website. It does not require a Pinterest account, password or personal session cookie, and does not launch a browser.
What happens to invalid or unavailable inputs?
Invalid individual inputs are saved as failed rows without a source request. Confirmed unavailable targets stop without unnecessary retries. Temporary failures allow up to five total attempts; other inputs and previously saved results remain available.
Can I export results or schedule runs?
Yes. Download the default dataset in supported formats or retrieve it through the Apify API. Apify schedules and completion webhooks can connect repeated runs to your own workflow.
Support, responsible use, and related actors 🛟
For a reproducible issue, use the Actor’s Issues tab and provide the run ID, approximate time, safe public input, expected behavior and actual result. Include the selected mode or page count when applicable. Do not share access tokens, cookies or proxy credentials.
Use public data responsibly and follow applicable privacy, copyright, contractual and platform requirements before storing, analyzing or redistributing collected information.
