Pinterest Keyword Autocomplete Scraper
Pricing
from $4.99 / 1,000 results
Pinterest Keyword Autocomplete Scraper
A robust, high-performance utility designed for developer automation, data integration, and AI training. Features built-in captcha bypass, headful/headless browser execution, and proxy support to scrape Pinterest Keyword Autocomplete data seamlessly, reliably, and at scale.
Pricing
from $4.99 / 1,000 results
Rating
0.0
(0)
Developer
Coding Frontned
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Share
Discovers public Pinterest search autocomplete suggestions for bounded keywords and locales. The Actor opens Pinterest's normal public search UI and reads the typeahead response that the page itself generates; it does not spoof browser automation signals, rewrite Pinterest responses, sign in, or call private account surfaces.
Features
- Multi-keyword support — get suggestions for multiple keywords in one run
- Locale-aware — supports regional locales (en_US, en_GB, fr_FR, de_DE, and more)
- Rich suggestion data — suggestion text, display name, type, category, image preview
- Bounded processing — choose concurrency from 1 to 3, with 1 as the conservative default
- Cloud-ready — runs on Apify with scheduling, proxy rotation, and webhook support
Use Cases
- Pinterest SEO keyword research and optimization
- Identifying trending search terms on Pinterest
- Content planning and topic discovery
- Building keyword datasets for Pinterest marketing campaigns
Input
| Field | Type | Default | Required | Description |
|---|---|---|---|---|
keywords | array | — | ✓ | List of seed keywords to get autocomplete suggestions for (e.g. ["interior design", "yoga"]). |
locale | string | en_US | Pinterest locale for region-specific suggestions (e.g. en_US, en_GB, fr_FR, de_DE). | |
maxItems | integer | 200 | Maximum total suggestions across all keywords. | |
maxConcurrency | integer | 1 | Public pages processed concurrently, from 1 to 3. | |
requestDelayMillis | integer | 1000 | Bounded wait before reading each page-generated response. | |
maxRequestRetries | integer | 2 | Page retries, from 0 to 3. | |
requestTimeoutSecs | integer | 90 | Per-page timeout, from 30 to 180 seconds. | |
proxyConfiguration | object | direct/no proxy | Optional Apify or custom proxy. Explicit setup failures stop the run. |
Output
Each suggestion includes:
| Field | Description |
|---|---|
inputKeyword | The original keyword you provided |
suggestion | The autocomplete suggestion (lowercase) |
displayText | Display text as shown by Pinterest |
annotation | Additional annotation or subtitle (when available) |
type | Suggestion type (e.g. suggestion, trending) |
category | Category context (when available) |
imageUrl | Preview image URL for the suggestion |
score | Relevance score (when available) |
resultCount | Estimated result count for the suggestion |
locale | Locale used for the query |
scrapedAt | ISO 8601 timestamp of scrape |
Sample Output
{"inputKeyword": "interior design","suggestion": "interior design living room","displayText": "interior design living room","type": "suggestion","suggestionUrl": "https://www.pinterest.com/search/pins/?q=interior+design+living+room","locale": "en_US","source": "Pinterest public search typeahead","pageType": "autocomplete_suggestion","scrapedAt": "2026-05-21T10:00:00.000Z"}
Notes
- Proxy: Direct public access is the default. Configure a proxy only when your authorized network requirements call for one; explicit proxy configuration is never silently ignored.
- Suggestion count: Pinterest typically returns 8–12 autocomplete suggestions per keyword. Actual count depends on search volume.
- Locale impact: Different locales return different regional suggestions. Use the locale matching your target audience.
- No-data behavior: A keyword with no public suggestions emits a diagnostic row. If all keywords produce only diagnostics, the run fails after preserving those rows and
OUTPUT_SUMMARY.
Quality checks
Run npm test for regression coverage and npm run validate for local dataset output. Exported cloud JSON can be piped to node validate-datasets.js - to apply the same required-field, provenance, URL, duplicate, locale, media-host, and timestamp gates.