Pinterest Detailed Data Extractor: 3 Practical Use Cases

Direct answer

Scrape Pinterest pins, profiles, boards, search results, and comments. Extract images, videos, metadata, and engagement stats using Pinterest's internal API. To apply this Actor effectively, select one clear operational task, define the evaluation criteria and final report format, and execute a small input run. The three playbooks outlined below demonstrate how digital marketers, e-commerce managers, and SEO strategists convert raw JSON output into structured, decision-ready data.

Practical use cases

These use cases come from Pinterest Detailed Data Extractor's published documentation. Each is expanded into an operating pattern so the Pinterest Detailed Data Extractor output has a purpose beyond collection.

Use case 1: Pin-level content, SEO, product, and

Outcome: Pin-level content, SEO, product, and destination research.

Question to answer: Once records are grouped fairly, which comparisons actually hold up and which were an artifact of the grouping?

Configure: Start with startUrls (List of Pinterest URLs to scrape. Supports pin URLs, user profile URLs, board URLs, and search URLs.), pinUrls (Public Pin links or numeric Pin IDs.), pinterestUrls (Compatibility alias for Pin URLs or IDs.). Use the narrowest Pinterest Detailed Data Extractor values that represent the real task, keep the first result set small, and record why each selected input matters to the Pinterest Detailed Data Extractor outcome.

Working method: Decide the comparison axis first, then place every record into a cohort before looking at outcomes. Keep raw and normalized values side by side, and review the records that do not fit any cohort instead of dropping them.

Deliverable: Create a ranked comparison brief listing each cohort, its defining fields, and the specific gap that matters for the decision. Include the Pinterest Detailed Data Extractor source identifier and the collected fields behind every Pinterest Detailed Data Extractor decision.

Stop condition: Pause when a cohort has too few records to compare fairly, the normalization hides a real difference, or the comparison is being driven by one outlier. Fix the Pinterest Detailed Data Extractor question, comparison rule, or configuration before expanding the Pinterest Detailed Data Extractor run.

Use case 2: Board inventories and large board-feed

Outcome: Board inventories and large board-feed exports.

Question to answer: Once duplicates are grouped, which stories are left, and what specific angle earns each one a place?

Configure: Start with startUrls (List of Pinterest URLs to scrape. Supports pin URLs, user profile URLs, board URLs, and search URLs.), boardUrls (Public board links or username/board-name paths.), boards (Compatibility alias for Board URLs.). Use the narrowest Pinterest Detailed Data Extractor values that represent the real task, keep the first result set small, and record why each selected input matters to the Pinterest Detailed Data Extractor outcome.

Working method: Score each candidate item on audience fit, novelty, and source diversity before selecting anything, and group near-duplicate items so only the strongest version of a story gets chosen.

Deliverable: Create a curation log listing each selected item, its cluster, and the specific reason it beat the alternatives in that cluster. Include the Pinterest Detailed Data Extractor source identifier and the collected fields behind every Pinterest Detailed Data Extractor decision.

Stop condition: Pause when the same handful of sources dominate every batch, novelty cannot be judged against recent history, or duplicate stories are being counted as separate items. Fix the Pinterest Detailed Data Extractor question, comparison rule, or configuration before expanding the Pinterest Detailed Data Extractor run.

Use case 3: Video and Story Pin discovery with real

Outcome: Video and Story Pin discovery with real media variants.

Question to answer: Applying the acceptance rule as written, which records clearly pass, clearly fail, and genuinely need a human call?

Configure: Start with startUrls (List of Pinterest URLs to scrape. Supports pin URLs, user profile URLs, board URLs, and search URLs.), enrichDetails (When enabled, each pin from search/profile/board results will be enriched with accurate stats (reaction count, follower count, etc.) by fetching its detail page. Slower but more complete data.), includeComments (When enabled, add one real comment/activity row for each collected Pin. Pinterest's public cookieless comment path is used automatically.). Use the narrowest Pinterest Detailed Data Extractor values that represent the real task, keep the first result set small, and record why each selected input matters to the Pinterest Detailed Data Extractor outcome.

Working method: Define what accepted, uncertain, and excluded mean before touching the first batch, write the rule down, and change only one rule or input at a time so you can see what actually moved the result.

Deliverable: Create a decision log where every record's classification is traceable to the specific field and rule that produced it. Include the Pinterest Detailed Data Extractor source identifier and the collected fields behind every Pinterest Detailed Data Extractor decision.

Stop condition: Pause when the acceptance rule cannot be applied consistently, required fields are frequently missing, or two reviewers reach different conclusions on the same record. Fix the Pinterest Detailed Data Extractor question, comparison rule, or configuration before expanding the Pinterest Detailed Data Extractor run.

Four steps to run the workflow

1. Identify the targeted Pinterest data task from the documented modes (pinDetail, userProfile, boardPins, or searchPins).
2. Configure input parameters in Apify, specifying limits such as maxItems, enrichDetails, or numeric filters like minSaves.
3. Execute the Actor task and inspect the progressive JSON response output for required source fields like pinId, followerCount, or seoTitle.
4. Export normalized dataset records to downstream analytics tools or spreadsheets for final review.

Input schema controls

Configure the collection task using these source-backed schema properties:

• mode: Select collection operational type (default: "auto"). Options include "pinDetail", "comments", "searchPins", "searchVideos", "userProfile", "userPins", "userBoards", "boardDetail", "boardPins", and "search".
• keywords: Array of search words or phrases for discovery runs.
• searchTerms: Compatibility alias array for search words.
• pinUrls: Array of public Pin URLs or numeric Pin IDs.
• pinterestUrls: Compatibility alias array for Pin URLs or IDs.
• usernames: Array of Pinterest usernames, handle strings with @, or public profile links.
• profiles: Compatibility alias array for Pinterest usernames.
• boardUrls: Array of public board links or username/board-name path strings.
• boards: Compatibility alias array for board URLs.
• search: Single string keyword search query.
• startUrls: Array of mixed public Pinterest URLs for auto-detect mode.
• maxItems: Integer limiting extracted items (default: 50, set to 0 for unlimited).
• maxPages: Integer capping pagination pages per feed (default: 0).
• minSaves: Integer threshold to filter Pins by save count.
• minCreatorFollowers: Integer threshold filtering Pins by creator follower count.
• verifiedOnly: Boolean retaining only verified accounts (default: false).
• requireOutboundLink: Boolean keeping only Pins with public outbound links (default: false).
• imageOnly: Boolean excluding video Pins (default: false).
• excludeAds: Boolean excluding sponsored or promoted Pins (default: false).
• commerceOnly: Boolean keeping only shoppable Pins with product metadata (default: false).
• includeComments: Boolean adding public comment rows per Pin (default: false).
• maxComments: Integer limiting comment rows per Pin (default: 10).
• cookies: Array containing Cookie Editor JSON export (optional, works without cookies).
• cookiesJson: String alias for Cookie Editor JSON export.
• endPage: Integer maximum pagination page limit (default: 0).
• enrichDetails: Boolean enabling detail page fetches for rich metadata (default: false).
• proxy: Object defining custom proxy configurations.
• proxyConfiguration: Object compatibility alias for proxy settings.

Fields returned by record type

The output contains four primary record_type values: pin, profile, board, and comment. Extracted properties reflect exact public data published by Pinterest:

• Pin fields: id, url, title, description, created_at, images, dominant_color, link, pinner_id, pinner_username, pinner_name, pinner_followers, board_id, board_name, board_url, save_count, comment_count, like_count, reaction_count, is_video, video_url, pinId, pinUrl, imageVariants, imageUrl, videoVariants, mediaType, pinFormat, storyPinId, altText, seoTitle, seoDescription, seoUrl, mobileLinkUrl, trackedLinkUrl, utmLinkUrl, domain, contentCategory, creatorFollowerCount, isPromoted, isShoppable, richMetadata, product.
• Profile fields: type, id, username, full_name, bio, follower_count, following_count, pin_count, board_count, image_url, website_url, is_verified, fullName, location, createdAt, followerCount, followingCount, pinCount, boardCount, profileViews, profileReach, isPrivate, isPartner, isVerifiedMerchant.
• Board fields: type, id, name, description, url, pin_count, follower_count, privacy, owner_username, boardId, pinCount, followerCount, sectionCount, collaboratorCount, coverImageUrl, isCollaborative.
• Comment fields: id, text, created_at, type, like_count, reply_count, author_name, author_username, author_id, pin_id, pin_url.

Frequently asked questions

Is account login required to run this scraper?

No account login is required. The actor operates over public, signed-out Pinterest endpoints. You may optionally supply session cookies via cookies or cookiesJson if specific account contexts are required.

Why does feed output return fewer items than an account's total pin count?

Public feed responses are constrained by Pinterest's internal index boundaries, active filters (such as imageOnly or minSaves), duplicate removal, and public visibility settings.

What additional data does setting enrichDetails enable?

Enabling enrichDetails forces the scraper to fetch each pin's full public detail page. This populates deep fields like seoTitle, seoDescription, full media variants, reaction breakdowns, and detailed product metadata.

How does the Actor handle zero values versus missing data?

Numeric zeroes and false boolean states published by Pinterest are preserved in the JSON payload. Unsupplied, missing, or private properties are omitted entirely rather than filled with empty guesses.

Can I extract public comments along with pin records?

Yes. By setting includeComments: true and specifying maxComments, the scraper automatically extracts public comment records using Pinterest's public cookieless activity path.

Resources

• Pinterest Detailed Data Extractor on Apify