Pinterest Scraper · Exact Saves for Search, Boards & Profiles

Scrape Pinterest pins by keyword search, board URL, profile or pin URL. Every pin becomes one flat, CSV-ready row with the exact save count Pinterest shows on the pin, saves per day, repins, reactions, comments, image, outbound link, board, pinner and an ISO creation date. No login, no Pinterest account, no cookies, no residential proxy.

Why this scraper

• The real save count, also for search results. Pinterest's search results do not include how often a pin was saved. This Actor fetches each search hit's own pin data to get the number shown on the pin, so search, boards and profiles all come back with the same saves field. The run summary says per source where each count came from (savesFromFeed, savesFromPinPage).
• Saves are not repins. Pinterest has two different counters. repin_count is often a small fraction of the saves: on pin 99360735500167749 it is 4,835 against 101,743 saves (measured 24 Sep 2026). You get both, in separate columns, so you never rank pins by the wrong number.
• Find the winners, not just the pins. savesPerDay (saves ÷ days since the pin was created) shows what is taking off right now instead of what is merely old. Sort each source by saves, savesPerDay or newest, or keep only pins above minSaves or newer than sinceDate.
• Flat rows. One level, no nested JSON: drops straight into Sheets, Excel or Airtable.
• You only pay for pins you get. Filtered pins, ads (promoted pins), duplicates across sources and inputs that fail are never charged. maxPins is a hard cap on the run and therefore on the bill. A source that returns nothing says why in the run summary instead of coming back empty.
• No residential proxy needed. Pinterest answered every request from Apify's own IPs (341 of 341 in the test run below), so runs stay cheap and nothing is billed to you as proxy traffic.

Input example

{
    "searchTerms": ["minimalist desk setup", "vegan meal prep"],
    "boardUrls": ["https://www.pinterest.com/marthastewart/american-made/"],
    "profileUrls": ["bhg"],
    "pinUrls": ["https://www.pinterest.com/pin/99360735500167749/"],
    "maxPinsPerSource": 200,
    "maxPins": 1000,
    "minSaves": 50,
    "sinceDate": "2026-01-01",
    "sortBy": "savesPerDay"
}

Any country domain works (de.pinterest.com, pinterest.co.uk, ...), and so do pin.it short links.

Output example

{
    "pinId": "99360735500167749",
    "url": "https://www.pinterest.com/pin/99360735500167749/",
    "title": "Next stop: Pinterest!",
    "description": "Love my Pinterest t-shirt!",
    "imageUrl": "https://i.pinimg.com/originals/a7/66/56/a76656e966b1958f568d63c3f1c05aec.jpg",
    "imageWidth": 640,
    "imageHeight": 478,
    "link": "http://www.flickr.com/photos/kentbrew/6851755809/",
    "domain": "flickr.com",
    "saves": 101743,
    "savesPerDay": 19.94,
    "repinCount": 4835,
    "reactions": 4,
    "comments": 35,
    "shares": 23,
    "isVideo": false,
    "videoUrl": null,
    "isPromoted": false,
    "board": "Adventures at Pinterest",
    "boardUrl": "https://www.pinterest.com/kentbrew/adventures-at-pinterest/",
    "pinner": "kentbrew",
    "pinnerName": "Kent Brewster",
    "pinnerFollowers": 4589,
    "createdAt": "2012-10-04T21:50:37.000Z",
    "ageDays": 5102.1,
    "hashtags": [],
    "altText": null,
    "dominantColor": "#e77b60",
    "sourceType": "pin",
    "source": "pinUrls",
    "rank": 1,
    "scrapedAt": "2026-09-24T00:00:00.000Z"
}

Field	Meaning
saves	The save count Pinterest shows on the pin, at scrape time
savesPerDay	saves ÷ age in days (minimum 1 day), 2 decimals
repinCount	Pinterest's separate repin counter, not the same as saves
reactions, comments, shares	As Pinterest reports them (shares only where Pinterest hands it out)
link, domain	Where the pin leads; empty for pins uploaded without a link
pinnerFollowers	Follower count of the account that saved the pin, where Pinterest includes it
createdAt, ageDays	ISO 8601 UTC; age at scrape time
sourceType, source, rank	How the pin was found (search, board, profile, pin) and its position there

The run summary (SUMMARY in the key-value store) lists per source: pins written, fetched, where the save counts came from, filtered out by reason, pages, why paging stopped, and HTTP status counts for the whole run.

Tested

Run on the Apify platform on 24 Sep 2026: one keyword, one board, one profile, 300 pins each requested. 893 pins written, 341 requests, all HTTP 200, no proxy. Three pins checked by hand against their pin pages: saves, repins, board and pinner matched exactly.

Honest limits

• Only what Pinterest shows logged out: public pins, boards and profiles. Secret boards, private profiles and comment texts are not included.
• Search needs one extra request per pin for the exact save count (turn off exactSaves for speed; saves then stays empty for search hits). Board and profile pins already carry saves.
• A board can return a few pins less than its pin counter says (293 of 299 on the test board): Pinterest counts pins it no longer serves.
• Some pins have no title; title is empty then rather than made up.
• sortBy orders the pins collected per source; it does not make Pinterest return a different set.
• Counts are a snapshot at scrape time.

Pricing (pay per event)

• Actor start: tiny flat fee per run
• Per pin written to the dataset. No charge for filtered pins, promoted pins, duplicates, or sources that return nothing.