Pinterest Trends Scraper & Keyword Research
Pricing
from $0.60 / 1,000 trend results
Pinterest Trends Scraper & Keyword Research
Get Pinterest trending keywords by market and category, or research your own keywords with weekly history, related terms, audience and a forecast where available. No login.
Pricing
from $0.60 / 1,000 trend results
Rating
5.0
(1)
Developer
Automation Lab
Maintained by CommunityActor stats
2
Bookmarked
618
Total users
126
Monthly active users
4 days ago
Last modified
Categories
Features
Share
Get Pinterest's trending keywords by market, category and season, or research your own keywords with weekly search history, related keywords, audience by age and gender and a forecast when Pinterest has one.
No Pinterest account, API key or proxy setup needed.
Best for
- Pinterest keyword research: check search interest, growth and audience for your own keywords.
- Content calendar planning around seasonal Pinterest search demand.
- Ecommerce product research for styles, categories, and gift/holiday themes.
- Agency reports comparing trend momentum across countries and trend types.
First run recipe
Run one market such as US, select one trend list, and set a small limit such as 25 results. A healthy first run returns ranked keyword rows with market, list, growth metrics when Pinterest exposes them, and a Pinterest Trends URL.
To research your own keywords, add them under Keywords to research and clear Trend types if you only want those keywords.
When to use this instead of Pinterest Scraper
Use this actor for trend and keyword intelligence before creating content, ads, or product pages. Use Pinterest Scraper when you need actual pins, boards, creators, or search-result content for a known keyword.
What does Pinterest Trends Scraper do?
Pinterest Trends Scraper works in two ways, and one run can do both.
Trend lists return Pinterest's growing, top monthly, top yearly and seasonal keywords, filtered by market, category, keyword and time window.
Keyword research takes up to 50 of your own keywords and returns one row per keyword and market, with weekly search history up to two years, week, month and year change, related keywords, audience by age and gender. US keywords also get Pinterest's 13-week forecast when Pinterest has one for that keyword.
The actor is built for content, ecommerce, social, and advertising research workflows.
Who is it for?
Content marketers
Plan articles, landing pages, and seasonal calendars around rising Pinterest demand.
Ecommerce teams
Spot product and style trends before they peak.
Agencies
Build client reports for different countries and trend types.
SEO researchers
Find visual-search keyword ideas that are not obvious in traditional SEO tools.
Social media teams
Translate trend momentum into boards, pins, campaigns, and creative briefs.
Why use this actor?
- 📈 Get trend keywords with growth metrics.
- 🌍 Compare countries and regional markets.
- 🔑 Research your own keywords with history, related terms, audience and a forecast when Pinterest has one.
- 🗂️ Filter trend lists by Pinterest category, or by included or excluded keywords.
- 🗓️ Choose trend windows and end dates.
- ⚙️ Export clean JSON, CSV, Excel, or API results from Apify.
Data you can extract
| Field | Description |
|---|---|
term | Pinterest trend keyword |
country | Market code |
trendType | growing, top_monthly, top_yearly, seasonal, or keyword for researched keywords |
rank | Row rank in the extracted result set |
normalizedCount | Pinterest normalized count when available |
searchCount | Search count score when available |
weeklyChange | Week-over-week change as a fraction: 0.25 means +25% |
monthlyChange | Month-over-month change as a fraction |
yearlyChange | Year-over-year change as a fraction |
seasonalityScore | Seasonal relevance score (trend lists) |
pinterestTrendsUrl | Deep link to Pinterest Trends |
dataDate | Date of the newest Pinterest data behind the row |
history | Keyword research: weekly search interest, 0-100 |
forecast | Keyword research, US only: 13 weekly points with lower and upper bounds, when Pinterest has a forecast for that keyword; otherwise empty |
relatedKeywords | Keyword research: related terms with latest, peak and average interest |
audience | Keyword research: share of searchers by gender and age group |
scrapedAt | Extraction timestamp |
How much does it cost to scrape Pinterest Trends?
The actor uses pay-per-event pricing.
You pay a $0.005 start charge per run and a per-result charge for each row saved: $0.00115 on the Free plan, $0.001 on Starter, $0.00078 on Scale, $0.0006 on Business. A researched keyword with its history, related keywords and audience counts as one result, the same as a trend-list row.
A run with 25 results costs about $0.03 on Starter. A run that finds no matching terms costs nothing.
From November 23, 2026, the per-result price will be $0.001 on Free and Starter, $0.0009 on Scale, and $0.0008 on Business and above. The start charge stays $0.005.
How to use Pinterest Trends Scraper
- Open the actor on Apify.
- Choose one or more country codes.
- Select trend types.
- Set the maximum results per country and type.
- Optionally add keyword filters.
- Run the actor.
- Download the dataset or consume it through the API.
Input options
Countries
Choose one or more supported markets from the input selector. Pinterest exposes some countries only as regional markets; the Actor automatically resolves those selections and reports the canonical regional code in country.
Examples:
US,CA,DE,FR,IT,ES,MX,BRGB+IEfor Great Britain and IrelandAU+NZfor Australia and New ZealandCHorAT→DE+AT+CH(Pinterest's Germanics market)SE,DK,FI, orNO→SE+DK+FI+NO(Pinterest's Nordics market)NL,BE, orLU→NL+BE+LU(Pinterest's Benelux market)
Unsupported free-form codes now fail before extraction with a clear validation error. Use the selector as the current source of supported country and regional options.
Trend types
Choose one or more:
top_monthlytop_yearlygrowingseasonal
Maximum results
maxResultsPerCountry is an upper bound for each market and trend type. Pinterest's filtered table exposes at most 100 rows per request; larger limits fetch the available table (up to 100), rather than sending a rejected oversized request. Filters and source availability can return fewer rows. The Actor does not invent additional pages or broaden your filters.
Categories
Pick from Pinterest's 22 categories, such as Beauty or Home decor, to limit trend lists. interestIds also accepts Pinterest's numeric IDs and category names.
Keyword research
Add up to 50 keywords. Each keyword and market returns one row. Use historyDays to choose 90, 180, 365 or 730 days, and turn includeForecast, includeRelatedKeywords or includeAudience off if you do not need them. Keywords Pinterest has no data for are skipped and not charged. Capitals do not matter.
The forecast appears when Pinterest has one for that keyword, for US keywords only, and only from Pinterest's latest data date.
endDate is optional and keyword research normally uses Pinterest's latest data. A later date uses the latest data and the run status says so. Pinterest accepts keyword end dates up to one year back, or up to 28 days before its latest data with historyDays 730. An older date stops the run before any charge and names the range.
Keyword filters
Use keywordsToInclude to focus a trend list on a topic.
Use keywordsToExclude to remove irrelevant terms.
Lookback window
Supported windows:
7D30D90D180D365D
Example input
{"countries": ["US", "CA"],"trendTypes": ["growing"],"maxResultsPerCountry": 25,"lookbackWindow": "30D","keywordsToInclude": ["nails"]}
Example output
{"term": "may nails","country": "US","trendType": "growing","rank": 3,"normalizedCount": 41,"searchCount": 41,"weeklyChange": -0.3,"monthlyChange": 6,"yearlyChange": 1,"seasonalityScore": 0.8292736,"pinterestTrendsUrl": "https://trends.pinterest.com/detail/?terms=may+nails&country=US","scrapedAt": "2026-05-23T00:00:00.000Z"}
Keyword research input:
{"countries": ["US"],"trendTypes": [],"keywords": ["christmas nails", "fall outfits"],"historyDays": "365"}
Keyword research output (shortened):
{"term": "nails","country": "US","trendType": "keyword","normalizedCount": 53,"weeklyChange": -0.05,"monthlyChange": -0.1,"yearlyChange": null,"dataDate": "2026-11-03","history": [{"date": "2026-10-27","count": 57},{"date": "2026-11-03","count": 53}],"forecast": [{"date": "2026-11-10","count": 65,"lowerBound": 59,"upperBound": 72}],"relatedKeywords": [{"term": "nails inspo 2026","latestCount": 67,"peakCount": 100,"averageCount": 28.87},{"term": "nail designs 2026","latestCount": 58,"peakCount": 100,"averageCount": 27.57}],"audience": {"gender": {"male": 0.04,"female": 0.92,"unspecified": 0.06},"age": {"18-24": 0.48,"25-34": 0.33,"35-44": 0.12,"45-49": 0.04,"50-54": 0.04,"55-64": 0.04,"65+": 0.04}}}
Tips for better results
- Start with one country and one trend type.
- Increase
maxResultsPerCountryafter validating the output. - Use keyword filters for niche research.
- Compare
growingandseasonaltrend types for campaign planning. - Use regional codes such as
GB+IEorAU+NZwhen Pinterest groups markets.
Integrations
Content calendar workflow
Run weekly and send results to Google Sheets, Airtable, or Notion.
Ecommerce workflow
Filter by product terms and send rising trends to a merchandising dashboard.
Agency reporting workflow
Run one market per client and export CSV reports.
SEO workflow
Use trend keywords as seed ideas for keyword research tools.
API usage
Node.js
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: process.env.APIFY_TOKEN });const run = await client.actor('automation-lab/pinterest-trends-scraper').call({countries: ['US'],trendTypes: ['growing'],maxResultsPerCountry: 25});console.log(run.defaultDatasetId);
Python
from apify_client import ApifyClientclient = ApifyClient('APIFY_TOKEN')run = client.actor('automation-lab/pinterest-trends-scraper').call(run_input={'countries': ['US'],'trendTypes': ['growing'],'maxResultsPerCountry': 25,})print(run['defaultDatasetId'])
cURL
curl -X POST "https://api.apify.com/v2/acts/automation-lab~pinterest-trends-scraper/runs?token=$APIFY_TOKEN" \-H "Content-Type: application/json" \-d '{"countries":["US"],"trendTypes":["growing"],"maxResultsPerCountry":25}'
MCP access
Use the Apify MCP server with Claude Code, Claude Desktop, Cursor, or VS Code.
MCP URL:
https://mcp.apify.com/?tools=automation-lab/pinterest-trends-scraper
Claude Code setup:
$claude mcp add --transport http apify-pinterest-trends "https://mcp.apify.com/?tools=automation-lab/pinterest-trends-scraper"
Claude Desktop setup (claude_desktop_config.json):
{"mcpServers": {"apify-pinterest-trends": {"url": "https://mcp.apify.com/?tools=automation-lab/pinterest-trends-scraper"}}}
Cursor setup: add the MCP URL as a remote HTTP server in Settings → Tools & MCP.
VS Code setup: add the MCP URL as an HTTP server in your workspace or user mcp.json.
Example prompts:
- "Run Pinterest Trends Scraper for US growing trends and summarize ecommerce ideas."
- "Compare Pinterest seasonal trends in US and CA."
- "Find Pinterest trend terms related to nails."
Supported countries
Pinterest controls market availability. The Actor's country selector reflects the currently verified standalone and grouped markets. If Pinterest removes a market or changes its grouping, the run fails clearly rather than returning misleading rows.
Limitations
Pinterest may change its public Trends endpoints.
Some countries, filters, or trend types can return fewer rows than requested. Pinterest returns at most 100 terms per list.
Pinterest publishes forecasts for the US only and not for every keyword, and search interest is a relative 0-100 score rather than an absolute search count.
The actor does not scrape individual pins, boards, or profiles.
Troubleshooting
Why did I get zero results?
Pinterest found no terms for that combination of market, filters and date. The run still succeeds, its status message says so, and nothing is charged. Try US with growing, remove keyword filters, and use a recent end date.
Brief Pinterest rate limits, server errors, and network interruptions are retried automatically. If the direct route keeps failing, the Actor retries that table through Apify's managed proxy route, within a per-run limit and at no extra charge to you. During a prolonged Pinterest outage the Actor stops early instead of working through every remaining table, and says how many tables it did not attempt, so you can retry them later. If one country/trend table still fails in a multi-market or multi-table run, other requested tables continue and useful results are retained. If Pinterest is unavailable for every table, the run fails and the message says so, so you can tell an outage from a search with no results.
Permanent request errors, such as an unsupported filter that Pinterest rejects with HTTP 400, are not retried. Correct the input before running again.
Why are some growth values null?
Pinterest does not return every metric for every trend row. Related keywords and audience can also be empty on a keyword row if those lookups failed; the status message says when that happened.
Can I scrape pins too?
This actor focuses on Trends. Use a Pinterest pin/profile scraper for pin-level data.
Legality
This actor collects publicly available trend data.
Make sure your use of the data complies with Pinterest terms, privacy laws, and your internal policies.
Do not use scraped data for spam, harassment, or unlawful profiling.
Data handling, AI, and affiliation
- The Actor sends the selected public market, filters and keywords only to Pinterest's public Trends endpoints. When the direct route keeps failing, the same public request goes through Apify's managed UNBLOCKER proxy, which handles it on Apify's infrastructure. It sends no cookies or credentials. It does not use AI or send data to an AI provider.
- It does not use a paid third-party data API, account, or credential. Charges are the documented start and per-result events; proxy use adds no charge.
- Failed operations send sanitized diagnostic input, exceptions, and Actor/build/run IDs to our private GlitchTip service for repair. Secret fields and URL queries are removed; diagnostic reports are retained for 30 days.
- It keeps no separate Actor-side result cache or external result copy. Run datasets, key-value stores, and logs follow your Apify account retention settings and can be deleted with Apify storage controls.
- Logs contain request market/type and operational counts, not secrets or user-private values.
- Pinterest is named only to identify the public source. This Actor is not affiliated with or endorsed by Pinterest.
Related actors
Verified public, non-deprecated actors that pair with this workflow:
- Pinterest Scraper — scrape pins, boards, and search results after trend discovery.
- TikTok Hashtag Scraper — compare short-form social demand.
- Google Trends Scraper — compare web-search trend signals.
- Instagram Hashtag Scraper — validate visual/social keyword demand.
Changelog
0.1
Initial version with Pinterest Trends keyword extraction.
Support
If you need a new field or market, open an issue on the actor page.
Output quality checklist
- One row per trend keyword.
- Numeric growth metrics where Pinterest provides them.
- Market and trend type on every row.
- Deep link back to Pinterest Trends.
Performance notes
The actor uses direct HTTP requests rather than a browser.
This keeps runs fast and cost-efficient. A normal successful request is made once; only transient HTTP 429/5xx or network failures trigger bounded retries, first direct and then through the managed proxy route.
Versioning
The actor follows semantic-ish Apify build versions.
Breaking output changes will be documented in this README.
FAQ
Does this require a Pinterest account?
No account is required for the current public Trends endpoints used by this actor.
Can I run multiple countries?
Yes. The actor loops over every selected country and trend type.
Can I schedule it?
Yes. Use Apify schedules to run daily, weekly, or monthly.
Server API: Pinterest Trends over HTTP
Pinterest Trends Scraper is also a Server Actor. Besides normal runs, it answers short HTTP requests directly, without starting a run for each lookup. Copy the server URL from the Actor's Server tab (do not build it from the Actor name) and authenticate with your Apify token. Use normal Actor runs for several markets or trend types at once, more than 10 keywords, a past end date, and up to 250 terms per market.
curl -sS "$SERVER_URL/trends?country=US&trendType=growing&maxResults=20" -H "Authorization: Bearer $APIFY_TOKEN"curl -sS "$SERVER_URL/keywords?keywords=christmas%20nails,fall%20outfits&country=US" -H "Authorization: Bearer $APIFY_TOKEN"
| Method and path | Input | Output and charge |
|---|---|---|
GET / | None | ready: true, the routes and limits; no scraping or charge |
GET /trends | Optional query country (market such as US, GB+IE, DE; a country such as AT maps to its regional market; default US), trendType (growing, seasonal, top_monthly, top_yearly; default growing), maxResults 1–100 (default 20), lookbackWindow (7D, 30D, 90D, 180D, 365D; default 30D), rankingMethod, interests (comma-separated category names or IDs, at most 20), keywordsToInclude, keywordsToExclude (comma-separated, at most 20 each) | {ok,count,results} with the same term records as a normal run's dataset items, in table order, ending today; one Trend result event (result) per returned term; no start fee |
GET /keywords | Query keywords: 1–10 comma-separated search terms; optional country (as above, default US), historyDays (90, 180, 365, 730; default 365), includeForecast (US only), includeRelatedKeywords, includeAudience (true/false, each default true) | {ok,count,results} with one keyword row per term that has Pinterest data, from Pinterest's latest data date; one Trend result event (result) per returned row; keywords without data are free; no start fee |
A request with no terms returns an error and is free. Each request has a 60-second deadline and a 1 MiB response cap, and one server works on at most eight requests at once. Nothing is cached. Errors use { "ok": false, "error": { "code": "...", "message": "...", "retryable": false } }: 400 INVALID_INPUT; 402 spending limit; 404 NO_RESULTS or unknown route; 405 wrong method; 413 RESPONSE_TOO_LARGE; 502 UPSTREAM_ERROR or charging failure; 503 server busy or stopping; 504 TIMEOUT. Failed requests are free. Retry only when retryable is true. The Server tab shows the full OpenAPI description.