Pinterest API

Scrape Pinterest data with one API

Name: Pinterest Data API
Brand: SocialCrawl
Availability: InStock

Fetch public Pinterest data as structured JSON with one SocialCrawl API key. Same Post, Comment, and Author schema as every other platform. Reads are priced in credits.

Read the docs How it works Try live

/v1/pinterest

5 active endpoints

GET /v1/pinterest/user/boards
GET /v1/pinterest/board
GET /v1/pinterest/pin
GET /v1/pinterest/search
GET /v1/pinterest/url-stats

What Pinterest endpoints does SocialCrawl ship?

5 live read endpoints for public Pinterest data. Boards, pins, search, and URL stats. Data API only.

User boards

1 credit

/v1/pinterest/user/boards

List Pinterest user boards.

handle, trim

Board

1 credit

/v1/pinterest/board

Get Pinterest board.

url, trim

1 credit

/v1/pinterest/pin

Get Pinterest pin details.

url, trim

Search

1 credit

/v1/pinterest/search

Search Pinterest pins.

query, cursor, trim

URL stats

1 credit

/v1/pinterest/url-stats

Get Pinterest save counts for external URLs.

urls

Pinterest API5 endpoints supported

View docs

Returns Pinterest pins matching a keyword, each with its title, image URL, save count, author info, and the board it belongs to.

Use it to discover pins on a topic; when you already have a pin URL, pin gives the fuller record.

1 credit

GET/v1/pinterest/search?query=home+decor+ideas

query

query · Search query

$ curl https://www.socialcrawl.dev/v1/pinterest/search?query=home+decor+ideas \
    -H "x-api-key: sc_YOUR_API_KEY"

idle

// Running this live needs your own API key. Hit "Try it" to see an example response

How the Pinterest API works

Pinterest is a normal SocialCrawl social surface. You call GET /v1/pinterest/… with an API key, spend credits on live misses, and get a single JSON envelope back. No second SDK.

Authenticate every call

Send your key in the x-api-key header. The same key works across the SocialCrawl catalog.

GET with query params

Routes are GET. Pass handles, urls, queries, and cursors as query strings. We validate formats before charging.

Pay in credits, not seats

Live misses debit the route tier. Cache hits cost 0. Empty or hard failures refund.

Read one JSON envelope

Every response is the same shape: success, data, credits_used, credits_remaining, request_id, cached.

The usual integration chain

Most products resolve an account, page content, then deepen only the posts that matter.

01Account

GET /v1/pinterest/user/boards

Author-shaped profile

Resolve the handle or id once.

02Feed

GET /v1/pinterest/board

PostList of recent public items

Page with cursor or after when the route supports it.

03Item

GET /v1/pinterest/pin

Full Post for one URL or id

List rows are not enough when you need the full record.

04Comments

GET /v1/pinterest/search

CommentList when the platform exposes it

Expand only when a thread matters.

request

GET /v1/pinterest/user/boards
  ?handle=pinterest
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_here

response envelope

{
  "success": true,
  "data": { "/* Author | Post | PostList | CommentList | … */": true },
  "credits_used": 1,
  "credits_remaining": 9999,
  "request_id": "req_…",
  "cached": false
}

What lands in data

Field names match the rest of SocialCrawl where archetypes align.

Authoruser/boards

id, username, display_name, avatar_url, bio, followers, url, ext

PostList / Postboard

items[].post with id, url, content, engagement, author, published_at, ext

CommentListpin

items[] with author, content.text, engagement, published_at when comments ship

Search / Mediasearch

search hits, media metadata, or transcripts depending on route

Inside the gateway

Same request lifecycle as every other /v1 platform endpoint.

Edge receives the call

Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit and concurrency.

Validate, then debit

Registry lookup finds the route. Required params run first. Invalid input returns 400 with no charge. Valid calls debit before upstream work.

Cache or fetch

A deterministic cache key is built from platform + resource + params. Hit: credits_used = 0. Miss: upstream fetch with retries and circuit breaker.

Normalize and return

Upstream JSON is mapped to Author / Post / PostList / CommentList (or route archetype), validated, wrapped in the success envelope, and logged for billing audit.

Billing rules that matter in production

Standard live miss: tier cost (often 1 credit)
Advanced reads: typically 5 credits
Premium reads: typically 10 credits
Metered routes: min floor when documented
Cache hit: 0 credits
Empty / hard fail: auto-refund
Bad params: 400, never charged
No credits: 402, never charged
Disabled routes: 503, never charged

How we get the data

Pinterest is public-read data on SocialCrawl. We normalize it into the shared schema so your code does not learn a second OAuth flow.

What Pinterest is for this API

Public Pinterest surfaces exposed by the registry. Read-only for research, monitoring, and product jobs.

How SocialCrawl reaches it

Social-read upstreams behind one gateway. Prism composites combine legs when a fat route is registered.

What leaves our edge

Unified JSON envelope: success, data, credits_used, request_id, cached. Shared Author / Post / Comment leaves where archetypes align.

What we do not ship live

No write endpoints and no private inbox. Disabled routes stay out of the active count. Prefer registry docs for the live inventory.

field map sketch

upstream identity→ author.* / data rootprofile identity and counters

public post / media→ post.* / items[].postpost content and engagement

list / search page→ items[] or hitscomments or search hits when present

What this API is used for

The jobs this API is most often used for.

5active Pinterest endpoints in the registry

1 / 5 / 10credit ladder across standard, advanced, premium

Pinterest monitoring and content intelligence

Callers concentrate on profile, content lists, search, and deepen paths on Pinterest. Structured Pinterest JSON on the shared schema with one SocialCrawl API key.

Detail reads are typically a few seconds on live miss. Search and fat composites are slower paths.

What people build with the Pinterest API

The jobs Pinterest data is most often used for. Each one is a full recipe with the endpoint chain and pricing.

Creator analyticsBoards and pins for creators whose output is visual.

Influencer discoveryPin and board search for creators whose work is visual.

Trend detectionPin search for visual and product themes that move ahead of the purchase.

Use case examples

Common ways teams put this data to work, and the stack each one tends to run.

Monitoring jobs

Python, cron, Slack bots

Poll profiles and feeds on Pinterest. Alert when engagement velocity jumps.

Research and VoC

Node, notebooks, BI loads

Search and expand posts for brand, product, and competitor language on Pinterest.

Backend product jobs

Go, workers, Explorer

Wire resolve to list to detail into pipelines. Cache hits keep recurring runs cheap.

Call it in two lines

Live misses spend credits by tier. Cache hits are free. Empty or hard failures refund.

curl "https://www.socialcrawl.dev/v1/pinterest/user/boards?handle=pinterest" \
  -H "x-api-key: sc_your_api_key_here"

curl "https://www.socialcrawl.dev/v1/pinterest/board?url=https://www.pinterest.com/lizmrodgers/moms-night/" \
  -H "x-api-key: sc_your_api_key_here"

Pinterest on SocialCrawl

Same key as the rest of the catalog

Platform docs Get an API key

Endpoints

What data does the Pinterest API return?

Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.

SearchSearch Pinterest pins PinGet Pinterest pin details Url StatsGet Pinterest save counts for external URLs BoardGet Pinterest board User BoardsList Pinterest user boards

Comparison

How does SocialCrawl compare to Official Pinterest API for Pinterest data?

Same Pinterest data, two very different paths. Auth, rate limits, schema, and cost, side by side.

Feature	SocialCrawl	Official Pinterest API
Authentication	One x-api-key header	OAuth 2.0 with access and refresh tokens
Setup & approval	Sign up and call in minutes, no app review	Developer app creation plus approval for most scopes
Rate limits	Credit-based: your only quota is your balance	Per-app rate limits you manage yourself
Response schema	Unified JSON shared across 51 platforms	Pinterest-specific response formats
Pricing	1 credit per request; 100 free credits on signup	Free, but limited to approved apps and scopes
Data coverage	Keyword search, pins, boards, user boards, URL save counts	Focused on managing your own content and ads
Maintenance	Schema stays stable. SocialCrawl absorbs upstream changes	You track API versioning and deprecations

Authentication

SocialCrawl

One x-api-key header

Official Pinterest API

OAuth 2.0 with access and refresh tokens

Setup & approval

SocialCrawl

Official Pinterest API

Developer app creation plus approval for most scopes

Rate limits

SocialCrawl

Credit-based: your only quota is your balance

Official Pinterest API

Per-app rate limits you manage yourself

Response schema

SocialCrawl

Unified JSON shared across 51 platforms

Official Pinterest API

Pinterest-specific response formats

Pricing

SocialCrawl

1 credit per request; 100 free credits on signup

Official Pinterest API

Free, but limited to approved apps and scopes

Data coverage

SocialCrawl

Keyword search, pins, boards, user boards, URL save counts

Official Pinterest API

Focused on managing your own content and ads

Maintenance

SocialCrawl

Schema stays stable. SocialCrawl absorbs upstream changes

Official Pinterest API

You track API versioning and deprecations

FAQ

Have a question? We got answers

Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.

How do I scrape Pinterest data with an API?

SocialCrawl provides 5 Pinterest API endpoints covering keyword search, pin details, board pins, user boards, and URL save counts. Send a GET request with your x-api-key. No OAuth, no Pinterest developer account, no business approval required.

What Pinterest endpoints does SocialCrawl offer?

5 endpoints: Search, Pin, URL Stats, Board, and User Boards. Every response uses the same unified schema.

Is there a free Pinterest API?

Yes. SocialCrawl's Pinterest API costs 1 credit per request on the standard tier, and new accounts get 100 free credits with no credit card required, enough for 100 Pinterest calls before you pay anything.

Does Pinterest have a public scraping API?

Pinterest's official API is gated behind business accounts and focuses on ads and conversions. SocialCrawl offers a direct scraping API for pins, boards, and search that works with any x-api-key, no Pinterest login, no OAuth.

How much does the Pinterest API cost?

All 5 Pinterest endpoints cost 1 credit per request on the standard tier. Get 100 free credits to start, then pay-as-you-go from £15/2.5k calls on Starter. Credits never expire, no monthly minimums, no rate limits.

Can I search Pinterest for pins by keyword?

Yes. The search endpoint takes a query parameter and returns matching pins with titles, image URLs, save counts, author info, and board details, ideal for visual trend research and content discovery.

What is the best Pinterest scraper API?

SocialCrawl is a strong choice for scraping public Pinterest data: 5 endpoints (search, pin, board, user boards, URL save counts) at 1 credit per request, with 100 free credits and no card. Unlike the official Pinterest API, there is no OAuth or business-account approval. One x-api-key returns unified JSON shared across 51 platforms.

How do I get Pinterest data via API?

Use SocialCrawl as your Pinterest data API: one x-api-key reads keyword search, pin details, board pins, user boards, and URL save counts as unified JSON. Pinterest does publish an official API, but it is gated behind business-account approval and built around managing your own content and ads, so SocialCrawl handles public reads instead, at 1 credit per request with 100 free credits on signup and no OAuth.

Is scraping Pinterest data legal?

SocialCrawl returns publicly available Pinterest data and does not access private or login-gated content. Whether scraping fits your project depends on your use case and jurisdiction. You are responsible for complying with Pinterest's terms of service and applicable data-protection laws such as GDPR and CCPA. This is general information, not legal advice.

Pinterest scraping API vs the official Pinterest API: what's the difference?

With SocialCrawl there is no app review or approval queue. Sign up and call Pinterest endpoints immediately with a single x-api-key. Responses share one unified schema with every other SocialCrawl platform, and credit-based pricing replaces per-platform quotas. Official APIs are still the right choice for posting and other write actions: SocialCrawl is read-only data.

Ask AI about SocialCrawl

Ask ChatGPT Ask Perplexity Ask Gemini Ask Claude Ask Grok

Read the Pinterest API reference in the docs

🤖 AI agent or LLM? Read this page as markdown