# Changelog of Pinterest Scraper & Trends — Pins, Boards, Profiles, Demand (`foxlabs/pinterest-scraper`) Actor

- **URL**: https://apify.com/foxlabs/pinterest-scraper/changelog.md
- **Full Actor documentation**: https://apify.com/foxlabs/pinterest-scraper.md

## Changelog

### 0.1.3 — 2026-10-01

- `maxPinsPerSource: 0` now means no pins at all: pin links are not read either. Each pin link gets a free `skipped` status row with the reason, and `SOURCE_REPORT.pinLinks.skipped` counts them, so a run with 0 has no `pin` or `pin-details` event. Before, pin links were read and delivered as `pin` rows even with 0.
- An input with only pin links and `maxPinsPerSource: 0` stops at once with the reason (nothing to deliver).
- README: keywords that mean nothing still return Pinterest's closest matches, and those pins are delivered and charged like any other.

### 0.1 — 2026-10-01

First version.

- Sources: search keywords, board links (pins in the board's sections included), profile links or usernames (created or saved pins), pin links or pin numbers. Any Pinterest country domain is accepted; pin.it short links are not (a free status row says so).
- Pin rows: title, description, alt text, Pinterest's topic labels, image and thumbnail, video flag and video link, outbound link and domain, product name, price, list price, discount and stock for product pins, reactions, created date, pinner with follower count, board, search rank.
- `includeDetails`: one more request per pin for saves, repins, comments, shares and the MP4 file of video pins; charged as `pin-details` only when the detail answer arrives.
- Pinterest Trends: weekly search-interest series per keyword (one year = 53 weekly values, or two years = 105) in 31 regions, with latest and peak week and week-, month- and year-over-year change. Keywords without Trends data get a free `no-trend-data` row.
- Free keyword summary per keyword: domains the pins link to (Pinterest's own image and page hosts left out), share of pins with a link, product pins, Pinterest's related searches, and the correction when Pinterest searched a corrected keyword (`pinterestQuery`, `autoCorrected`).
- `expandWithRelatedSearches`: when Pinterest ends a keyword's results (about 800–960 pins), continue with up to 10 of its related searches; rows carry `relatedQuery`. Related searches run in parallel and the pin limit holds exactly.
- `maxPinsPerSource: 0`: no pins from keywords, boards or profiles (Trends series, profile rows and free board rows only); pin links are always read.
- Video: `isVideo` marks video pins; `videoUrl` is set for videos Pinterest hosts (YouTube pins have none).
- Pins without an outbound link: most are uploads Pinterest marks "Uploaded by user"; collection pins keep their product links inside the collection, which this version does not read.
- Profile rows: followers, following, pins, boards, monthly views (Pinterest's "10M+" band kept as text), website and domain verification, verified merchant, business account, first 25 boards.
- Each pin is delivered and charged once per run, whichever source finds it first.
- Counts Pinterest does not give, or gives as -1, are `null`, never 0.
- Route: Apify datacenter proxy by default; Apify residential proxy after a block (HTTP 403/429) or two failures in a row; retries with back-off.
- Pricing events: `pin`, `pin-details`, `keyword-trend`, `profile`. Status, board and keyword-summary rows are free.
- `SOURCE_REPORT` record per run; every source that delivers nothing leaves a free status row with the reason.
- Batch and Standby (HTTP API: `/pins`, `/trends`) modes share the same code and events.
- Memory: 512 MB minimum (the largest local run, 2,500 pins with related searches, peaked at about 240 MB).