Pinterest Search Scraper

Search Pinterest by keyword and get clean, structured pins — image and video URLs, title, description, the destination link (where the pin actually goes), pinner, board, and repin/comment counts. No login.

Pinterest's web API rejects anything that doesn't look like a real browser session with the current app build, which is why naive scrapers just get Invalid Resource Request. This actor bootstraps a real session and the live build hash on every run, then paginates cleanly through the results.

Input

Field	Notes
query	Keywords, e.g. home office setup, minimalist tattoo.
maxItems	Pins to collect; the scraper paginates to reach it.
includeVideosOnly	Only video pins (with the direct video URL).
includePromoted	Include sponsored pins (off by default).

Output

One row per pin: title, description, pinUrl, imageUrl, isVideo, videoUrl, link (destination), repinCount, commentCount, createdAt, pinnerUsername, pinnerName, boardName, boardUrl, dominantColor. Queries with no matches return a single note row and are not charged.

Nullable fields

Pinterest does not return every field for every pin, so some fields can be null even on otherwise complete rows:

• videoUrl can be null even when isVideo is true — Pinterest's API does not always include the playable video field for a given pin. Such pins are still real video pins; only the direct URL is missing.
• link (destination), description, repinCount, commentCount, createdAt, boardName, boardUrl, and dominantColor may also be null when Pinterest omits them for a pin.

Diagnostics & charging

Only genuine pins are charged (pay-per-result). Runs that are blocked, rate-limited, return no results, or are given bad input are never charged — instead a single diagnostic row (ok: false) is written to the dataset with a clear errorCode:

• BAD_INPUT — no query was provided.
• BLOCKED / RATE_LIMITED — Pinterest blocked or throttled the IP; retry with a residential proxy.
• NO_RESULTS — the query succeeded but matched no pins.
• NETWORK / SERVER_ERROR — a transient connectivity or Pinterest server error; retry later.

If you request more pins than you receive, it usually means Pinterest's relevance ranking simply ran out of fresh results for that query (the scraper stops after two consecutive empty pages), or the IP was rate-limited — check for a diagnostic row to tell the two apart.

Notes

A residential proxy is recommended — Pinterest geolocates and rate-limits datacenter IPs. Results follow Pinterest's own relevance ranking for the query.