Pinterest Data Scraper

Keep Pinterest profiles and published work in a searchable file. Using Pinterest URLs, the result preserves titles, pinner username, oembed author names, repin count, and pin identifiers in source order.

The record

The dataset schema names every field before the run. The first working set is pinId, title, description, seoTitle, seoAltText, pinnerUsername, pinnerId, pinnerDomain, boardId, boardUrl, domain, and link. Dataset views keep related fields together without changing the underlying row.

Captured row

{
  "boardId": "99360804217844427",
  "canonicalPinId": "485825878526052520"
}

Input

Pinterest Data Scraper accepts source URLs. Run controls stay in the same form.

Field	What it controls	Starting value
startUrls	Paste exact Pinterest URLs, one per line.	["https://www.pinterest.com/pin/99360735500167749/"]
maxItems	Stop after this many dataset rows.	20
maxSeconds	Stop after this many seconds and keep completed rows.	180

Example input

{
  "startUrls": [
    "https://www.pinterest.com/pin/99360735500167749/"
  ],
  "maxItems": 1,
  "maxSeconds": 180
}

Price

$10 per 1,000 pins on the Free plan. Other Apify plans use the rates shown in the Pricing tab.

Console, API, schedules, and exports

Runs can begin in Apify Console, from a saved task, or through the Actor API. A schedule can reuse the same input. Completed rows remain in the run dataset for API retrieval and Apify dataset exports.

POST https://api.apify.com/v2/acts/qe27rtx3HD3IK7HBd/runs
GET  https://api.apify.com/v2/datasets/{datasetId}/items

Saved tasks

Twenty task pages cover distinct research, comparison, operations, automation, and export jobs. The opening set is:

• Pinterest data exact query: Review one Pinterest record around title, pinnerUsername, boardUrl, and domain. The saved task uses startUrls, maxItems, and maxSeconds and opens the overview view. Configured in Pinterest Data Scraper.
• Pinterest data query comparison: Compare Pinterest records using repinCount, commentsDisabled, title, and seoTitle. The identity view keeps the differences close together. Configured in Pinterest Data Scraper.
• Pinterest data query list: Process a saved Pinterest input queue with startUrls, maxItems, and maxSeconds. Source and identifier fields remain visible in the source view. Configured in Pinterest Data Scraper.
• Pinterest data result index: Index Pinterest records by title, seoTitle, seoAltText, and pinnerUsername. The saved input keeps the same matching keys from run to run. Configured in Pinterest Data Scraper.
• Pinterest data destination register: Assemble a Pinterest register centered on pinnerDomain, domain, boardUrl, and isCollaborativeBoard. The task keeps startUrls, maxItems, and maxSeconds visible for later review. Configured in Pinterest Data Scraper.
• Pinterest data ranking benchmark: Compare numeric and status fields across Pinterest records, led by repinCount, commentsDisabled, breadcrumbs, and visualTags. Results open as the engagement table. Configured in Pinterest Data Scraper.

Related products

• Pinterest Search Scraper
• Pinterest Profile Scraper
• Instagram Search Scraper
• Reddit Search Scraper
• Instagram Bulk Export Scraper

Support

Include the Actor ID, run ID, saved task name, and affected input when reporting an issue. That is enough to locate the run and its dataset.