Pinterest Data Extractor: Up to 1,000 Free Results a Month (2026)

Each record provides up to 95 Pin fields, 32 profile fields, 21 board fields, or 31 comment fields. Extraction costs $5.00 per 1,000 results on Apify's free plan, which includes $5.00 of monthly prepaid usage. You can target search terms, profiles, boards, or specific Pins across 11 different modes using 28 optional controls. This Actor is built for growth teams, content strategists, and researchers who need raw Pinterest engagement data, board structures, and media URL variants. It is not for anyone who needs to download raw image files or video binaries directly, which requires a dedicated storage actor like Pinterest Media Downloader.

Try it before you read further. Apify's free plan includes $5.00 of usage every month with no credit card, enough for up to 1,000 results at $0.005 each before platform usage. Open Pinterest Data Extractor on Apify and run the prefilled example.

How reliable is Pinterest Data Extractor in production?

Across the last 30 days of public runs on the Apify platform, Pinterest Data Extractor recorded 93 runs with the following outcomes.

No run failed or timed out in the last 30 days. Keep a retry and an alert on scheduled runs all the same: a clean month is a record, not a guarantee.

What does it cost to run Pinterest Data Extractor?

Each result costs $0.005 on Apify's free plan, which is $5.00 per 1,000 results. Starting a run is charged separately at $0.005 per GB of Actor memory. Apify also bills the platform usage each run consumes, at the rates of your Apify plan, on top of these charges.

Worked example: collecting 10,000 results costs $50.00 in result charges before run-start fees and platform usage. No run failed or timed out in the last 30 days, so the list price is a fair budget; keep a retry in place all the same.

Total run expenses are driven by dataset size, which depends directly on the maxItems setting and the number of targets provided in keywords, usernames, or boardUrls. Toggling boolean flags like enrichDetails or includeComments increases field depth or item counts without altering the base per-result price. To test extraction rules cheaply, keep maxItems set to a low value like 10 before launching un-capped tasks.

How do you run Pinterest Data Extractor from the API?

None of its 28 controls is strictly required, so the defaults below produce a valid run on their own. Nothing in the payload below is illustrative. Those are the schema's prefilled defaults for Pinterest Data Extractor, so the request works once your token is in place.

Call the synchronous endpoint to start a run and receive dataset items in one request:

curl -X POST "https://api.apify.com/v2/acts/crawlerbros~pinterest-data-extractor/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"search":"cats","startUrls":[],"proxy":{"useApifyProxy":true}}'

The same run from Python, using the official client:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")

run_input = {
  "search": "cats",
  "startUrls": [],
  "proxy": {
    "useApifyProxy": True
  }
}

run = client.actor("crawlerbros~pinterest-data-extractor").call(run_input=run_input)

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

And from Node.js:

import { ApifyClient } from 'apify-client'

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' })

const input = {
  "search": "cats",
  "startUrls": [],
  "proxy": {
    "useApifyProxy": true
  }
}

const run = await client.actor('crawlerbros~pinterest-data-extractor').call(input)
const { items } = await client.dataset(run.defaultDatasetId).listItems()
console.log(items)

Because the call is synchronous, your client waits for the whole run. Keep it for exploration. For scheduled work, start the run without waiting and collect the dataset afterwards, so network trouble costs you a retry rather than the results.

Which Pinterest Data Extractor inputs matter, and which can you skip?

The mode parameter dictates how the Actor interprets inputs, accepting options like auto, searchPins, or userProfile. For keyword extraction, feed target phrases into keywords, or supply profile handles inside usernames. Leave optional JSON parameters like cookies empty unless accessing private sessions, as all public endpoints work without authentication.

• search (string): Keyword to search on Pinterest. Results will be pins matching this query.
• startUrls (array): List of Pinterest URLs to scrape. Supports pin URLs, user profile URLs, board URLs, and search URLs.
• proxy (object): Proxy settings for the scraper. Uses Apify Proxy by default.
• mode (string): Choose a collection type. Auto-detect accepts mixed public Pinterest links. Default: "auto".
• keywords (array): One or more words or phrases for search modes. Default: [].
• pinUrls (array): Public Pin links or numeric Pin IDs. This is also accepted as pinterestUrls for compatibility. Default: [].
• usernames (array): Usernames, @usernames, or public profile links. Default: [].
• boardUrls (array): Public board links or username/board-name paths. Default: [].
• maxItems (integer): Maximum number of items to scrape. Set to 0 for unlimited. Default: 50.
• maxPages (integer): Maximum pagination pages per search, profile, or board. 0 means continue until Pinterest has no next page. Default: 0.
• minSaves (integer): 0 means no minimum. For a positive value, keep only Pins where Pinterest supplies a numeric save count at or above it.
• minCreatorFollowers (integer): Keep Pins only when Pinterest supplies a creator follower count at or above this value.

The other 16 controls, with their defaults, are listed in the input schema on Pinterest Data Extractor on Apify.

Fixed-choice controls: mode accepts 11 values (default auto), including auto (Auto-detect links), pinDetail (Pin details), comments (Comments for Pins), searchPins (Search Pins).

What does Pinterest Data Extractor return?

Returned dataset items provide structured metrics including save_count, follower_count, destination URLs, and media resolution arrays. They omit private account details, non-public analytics, and direct media file downloads. Use these records to analyze visual trends, track creator output, or index board structures.

Output per record

• record_type
• source_url
• scraped_at
• pin
• profile
• board
• comment

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
• reaction_counts
• is_video
• video_url
• pinId
• pinUrl
• imageVariants
• imageUrl
• videoVariants
• mediaType
• pinFormat
• storyPinId
• storyPages
• altText
• seoTitle
• seoDescription
• seoUrl
• mobileLinkUrl
• trackedLinkUrl
• utmLinkUrl
• domain
• contentCategory
• mediaMethod
• creator
• creatorId
• creatorUsername
• creatorName
• creatorFollowerCount
• originalCreator
• board
• boardId
• boardName
• boardUrl
• boardCoverImageUrl
• boardPinCount
• boardFollowerCount
• boardSectionCount
• boardCollaboratorCount
• boardPrivacy
• boardCreatedAt
• boardIsCollaborative
• boardFollowedByMe
• saves
• commentCount
• repinCount
• shareCount
• reactionCounts
• reactionCount
• likeCount
• linkUrl
• linkDomain
• isPromoted
• commentsDisabled
• commentsEligible
• isEligibleForImageDownload
• isEligibleForProduct
• isOutOfStock
• isStaleProduct
• isUnsafeForComments
• isDownstreamPromotion
• shouldMute
• richMetadata
• product
• isShoppable
• shoppingFlags
• canonicalUrl
• canonicalPinId
• canonicalPinUrl
• width
• height
• duration
• thumbnailUrl
• pageId
• layout
• type
• text
• videos

Profile fields

• type
• id
• username
• full_name
• bio
• follower_count
• following_count
• pin_count
• board_count
• image_url
• website_url
• is_verified
• profileId
• profileUrl
• fullName
• location
• createdAt
• followerCount
• followingCount
• pinCount
• boardCount
• monthlyViews
• avatarUrls
• avatarUrl
• websiteUrl
• domainUrl
• isPrivate
• isPartner
• isVerifiedMerchant
• isDomainVerified
• isTastemaker
• isVerified

Board fields

• type
• id
• name
• description
• url
• pin_count
• follower_count
• privacy
• owner_username
• owner_name
• boardId
• recordType
• createdAt
• pinCount
• followerCount
• sectionCount
• collaboratorCount
• coverImageUrl
• isCollaborative
• followedByMe
• ownerUsername

Comment fields

• id
• text
• created_at
• type
• node_id
• like_count
• reaction_counts
• reaction_by_me
• helpful_count
• marked_helpful_by_me
• reply_count
• is_edited
• is_highlighted_by_pin_owner
• is_translatable
• tags
• tagged_users
• media
• author_name
• author_username
• author_id
• author_first_name
• author_image
• author_image_medium
• author_node_id
• author_is_private_profile
• pin_id
• pin_url
• record_type
• source_url
• scraped_at
• false

These are the documented fields. Optional ones can be empty on a given record, so measure how often each field your deliverable depends on is populated across a real sample before automating the handoff.

How do you build the workflow end to end?

Open Pinterest Data Extractor and work through these in order. Each step ends with something to check, so a bad configuration surfaces on a small run rather than a scheduled one.

1. Select the extraction mode using mode, choosing searchPins for keywords or userProfile for accounts.
2. Supply target inputs in keywords for search phrases, or set usernames for profile extractions.
3. Set maxItems to 10 to check record structures before launching large collection runs.
4. Apply record filters by toggling excludeAds, commerceOnly, or imageOnly depending on requirements.
5. Enable enrichDetails if your dataset requires deep creator follower metrics or image resolution variants.
6. Verify that returned records contain expected field names like save_count or pinner_username in dataset view.
7. Set maxItems to 0 or a higher cap to run full automated pagination across feeds.

How do you apply it? Three worked playbooks

These are Pinterest Data Extractor's own documented use cases, each worked through as an operating pattern rather than a description.

Use case 1: Competitor Content Research

Outcome: Content and competitor research by keyword, creator, board, or Pin.

Configure: Set mode to "searchPins", keywords to ["kitchen decor", "modern lighting"], and maxItems to 500.

Working method: Start with target phrases in keywords and execute a test run. Compare engagement fields like save_count and comment_count across returned items. Identify top creators, then pass their handles to usernames with mode set to "userPins" to map out successful visual formats.

Deliverable: A structured dataset of Pin records containing save counts, comment metrics, creator IDs, and destination links.

Stop condition: Stop if returned items carry null save_count values across all records.

Use case 2: Media Reference Extraction

Outcome: Finding image and video references with destination links and media variants.

Configure: Set mode to "boardPins", boardUrls to ["https://www.pinterest.com/nasa/hubble-images/"], requireOutboundLink to true, and enrichDetails to true.

Working method: Pass specific board links into boardUrls. Inspect early records to confirm populated arrays inside imageVariants or videoVariants. Confirm that destination URLs reside in link or outbound link fields before raising maxItems.

Deliverable: A dataset of media records containing resolution variants, image URLs, thumbnail links, and outbound destination URLs.

Stop condition: Stop if media arrays fail to return explicit width and height dimensions across consecutive board Pins.

Use case 3: Directory Creation

Outcome: Building creator and board directories from public identity and count fields.

Configure: Set mode to "userProfile", usernames to ["nasa", "crazylaurablog"], verifiedOnly to false, and minCreatorFollowers to 1000.

Working method: Supply target account names into usernames. Verify output rows for complete count metrics in follower_count, following_count, and board_count. Pass discovered board paths to mode "boardDetail" to build full organizational structures.

Deliverable: A directory dataset containing user profiles, follower metrics, board counts, and verification statuses.

Stop condition: Stop if profile rows return missing profileId or handle identifiers.

What breaks, and how do you design around it?

• Over the last 30 days, 0.0% of public runs failed and 0.0% timed out. Build retries and alerting around those rates rather than assuming every run completes.

Pinterest occasionally limits deep feed pagination on broad search terms. When extraction caps prematurely, split broad search queries into specific multi-word phrases inside keywords or paginate directly via boardUrls. If full creator attribution is missing on search feeds, set enrichDetails to true to force individual item lookups.

When should you not use Pinterest Data Extractor?

Do not use this Actor if you need to save actual image or video media files to key-value stores. For bulk file downloads, use Pinterest Media Downloader instead. If your pipeline requires deep creator metadata, product markup, and Story Pin layouts, use Pinterest Detailed Data Extractor. Avoid this Actor if you are attempting to collect private user data or bypass non-public access controls.

What should you check before trusting the output?

• Verify record_type is present on every item to distinguish pins, profiles, boards, and comments.
• Check for missing creatorId or pinner_username fields when creator attribution is required.
• Ensure save_count carries an explicit numeric integer rather than missing keys when minSaves is active.
• Confirm that link contains a valid URL string when requireOutboundLink is set to true.
• Set alert triggers if a run returns zero dataset items when valid keywords or boardUrls were passed.

None of this proves a record is correct. It gives a scheduled Pinterest Data Extractor run defined points where it should stop instead of quietly passing bad data downstream.

Frequently asked questions

What does it cost to extract 1,000 Pinterest pins?

Extracting 1,000 results costs $5.00 on Apify's free plan. Paid Apify tiers offer lower per-result pricing. Apify's free plan includes $5.00 of monthly prepaid usage, letting you collect up to 1,000 results without paying extra.

How reliable is Pinterest Data Extractor for scheduled jobs?

Over the last 30 days, 93 of 93 public runs finished successfully with zero failures and zero timeouts. This execution history makes it dependable for scheduled tracking pipelines.

Do I need to supply Pinterest cookies or account logins?

No. The Actor extracts public Pinterest Pins, creator profiles, boards, and comments using cookieless endpoints. Optional cookie parameters exist only for specialized session exports.

Can I filter out promoted or sponsored Pins?

Yes. Set excludeAds to true in the input schema to automatically drop Pins that Pinterest marks as promoted or sponsored from your final dataset.

Why are some fields omitted from certain dataset rows?

Pinterest does not publish every metadata field for every item type. The Actor preserves published zeroes and explicitly returned false values, but omits fields that Pinterest does not provide.

Where to go next

When you are ready to run it, open Pinterest Data Extractor on Apify; the free plan covers up to 1,000 results a month.

Start with the Pinterest Data Extractor Actor page for the current input schema, pricing tier, and run history.

It is part of the Pinterest Scraping Suite, which puts every related Actor on one page with its price and run history.

If you are comparing approaches rather than committing to one Actor, these category pages list every option we publish:

• Comment scrapers covers 37 Actors in this family.

Readers running Pinterest Data Extractor commonly pair it with:

• Pinterest Detailed Data Extractor: Scrape Pinterest pins, profiles, boards, search results, and comments.
• Pinterest Media Downloader: Download images and videos from Pinterest pins in bulk.
• Pinterest Scraper Pro: Scrape Pinterest pins, board pins, user boards, and user profiles.
• Pinterest Comments: Collect public Pinterest comments, Tried It activity, comment authors, and engagement from Pin URLs without requiring login cookies.
• Pinterest Trends: Collect Pinterest public featured trends, editorial trends, shopping categories, and trend time series by region.

Related guides:

• Pinterest Detailed Data Extractor: 3 Practical Use Cases
• Pinterest Scraper Pro: 3 Practical Use Cases
• YouTube Video Details Scraper: Up to 1,000 Free Results a Month (2026)
• TikTok Post Scraper Integration Guide and Operating Playbooks
• Social Media Finder: Operating Guide and Cross-Platform Playbooks

Resources

• Actor documentation, input schema, and pricing: verified against the published Actor on 2026-09-24.

• Actor last updated by its maintainers on 2026-09-14.

• Run outcome figures cover the 30 day public window ending 2026-09-24.

• Pinterest Data Extractor on Apify