Visual trend research
Collect pin and search signals to understand visual demand and content themes.
Pinterest Data API
Supported API
Pinterest Data API for pins, profiles, and visual search
Build visual discovery, product research, and content intelligence workflows with Pinterest API methods for pins, profiles, and search surfaces.
ScrapeStorm is not affiliated with Pinterest. Use the API only for permitted data workflows.
What you can build
Pinterest coverage is grouped into pin, profile, and search surfaces for quick product mapping.
Profile enrichment
Add Pinterest profile context to creator, brand, or product datasets.
Catalog intelligence
Support merchandising and inspiration tools with structured pin-oriented data.
Entity directory
All supported entities
Browse every supported Pinterest entity below, understand what each surface is for, and open the exact docs that matches your workflow.
Pinterest profile data
2 API methodsProfile API methods resolve public identity, account context, and the base layer for creator, brand, or people-oriented products.
What you get. Use this entity to fetch account details, contacts, summary context, and the identifiers you need before moving into content or social API methods.
API methods inside this entity
2 API methods
Open the API method that matches the lookup, feed, summary, or discovery job you need.
API methods inside this entity
2 API methods
Open the API method that matches the lookup, feed, summary, or discovery job you need.
Profile: Boards by username
Open docsOpen these docs when you need the actual profile content surface for monitoring, archive jobs, or reporting workflows.
Profile: Board metrics by username
Open docsChoose this API method when your product needs a compact performance view around profile without opening a larger content collection.
Pinterest pins data
2 API methodsPin API methods focus on saved visual content and the public discovery context around it.
What you get. Use this group for product research, creative inspiration, and visual trend workflows that need item-level content access.
API methods inside this entity
2 API methods
Open the API method that matches the lookup, feed, summary, or discovery job you need.
API methods inside this entity
2 API methods
Open the API method that matches the lookup, feed, summary, or discovery job you need.
Pins: Comments by pin ID
Open docsUse this API method to inspect the public conversation around pins and understand how people are reacting to the content.
Pins: Details by pin ID
Open docsStart here when you need richer public context behind pins: Details by pin ID and want the most complete identity view first.
Pinterest search data
3 API methodsSearch API methods expose public discovery surfaces, queries, and intent signals across the platform.
What you get. This entity is a natural entry point for research, prospecting, alerting, and products that need to find people, content, or topics fast.
API methods inside this entity
3 API methods
Open the API method that matches the lookup, feed, summary, or discovery job you need.
API methods inside this entity
3 API methods
Open the API method that matches the lookup, feed, summary, or discovery job you need.
Search: Pins by query
Open docsUse this API method for discovery work around search when you need to find relevant public accounts, topics, or content quickly.
Search: Pin metrics by query
Open docsChoose this API method when your product needs a compact performance view around search without opening a larger content collection.
Search: Suggestions by term
Open docsUse this API method for discovery work around search when you need to find relevant public accounts, topics, or content quickly.
How teams move from evaluation to launch
Each platform page follows the same decision path: choose the data surface, inspect the docs, validate the response, then scale with pricing and status visibility.
-
01
Map the platform surface
Use the coverage map to identify the entity group that matches your product workflow.
-
02
Open representative docs
Review the implementation docs for method, path, query parameters, and response shape.
-
03
Normalize into your product model
Prefer V2 API methods when you need stable fields across dashboards, scoring, or enrichment jobs.
-
04
Monitor price and status
Check API method pricing and operational status before moving a workflow into production.
Start here
First request
Begin with one Pinterest API method and open its docs for required fields and response examples.
API method
Profile: Boards by username
Request cost
2 credits
Required parameters
usernamestrcurl --request GET \
--url "https://www.scrapestorm.net/api/v2/pinterest.com/profile/boards-by-username" \
--header "X-API-Key: 00000000-0000-4000-8000-000000000000" \
--get --data-urlencode 'username=value' \
# Optional parameters:
# --data-urlencode 'cursor=QVFB...'
# --data-urlencode 'sort=last_pinned_to'
Auth header
X-API-Key
Required parameters
username
Billing event
2 credits per successful response
Launch details
Pricing, monitoring, and launch details
Pinterest methods are listed with credit prices and grouped by version in the pricing catalog.
ScrapeStorm is not affiliated with Pinterest. Use the API only for permitted data workflows.
API methods7
Entities3
Credits2 credits
Per-success credit pricing
API method prices are visible before integration and credits are tied to successful API responses.
API reference and implementation docs
Each platform page links to the API reference and implementation docs for exact request and response details.
Responsible data use
ScrapeStorm is independent from the listed platforms; your team remains responsible for permitted data processing.
Adjacent APIs
View all platforms
Related platform data APIs
Questions before launch
These answers cover coverage, pricing, response formats, and launch details before you commit engineering time.
Can Pinterest API methods be used for search products?
Yes. Search API methods are listed where available and linked to per-method implementation docs.
Are pin and profile responses normalized?
Use V2 methods when you want normalized ScrapeStorm response structures.