Pinterest scraper API
Search public pins, resolve pin metadata, list profile boards, and page board pins over REST. Same JSON envelope as Instagram and TikTok — no Pinterest-only scraper to keep alive.
Why teams use Social Fetch for Pinterest
Pinterest is where product discovery still looks like shopping: mood boards, saved pins with outbound product links, and keyword searches that surface seasonal demand before it shows up on TikTok. Commerce teams, agencies, and enrichment products need that visual graph next to Instagram and TikTok creator rows — not a separate HTML parser that dies every time Pinterest tweaks infinite scroll.
Homegrown Pinterest scrapers break on signed assets, region quirks, and board pagination. What most pipelines actually need is narrower and more boring: search pins by query for trend and assortment research, hydrate a known pin URL into title / image / destination link / save counts, list the public boards on a brand or creator handle, then walk the pins on a board URL into warehouse rows.
Social Fetch exposes those four jobs as ordinary GET routes under `/v1/pinterest/...`. You pass a query, pin URL, handle, or board URL and get structured JSON with `data.lookupStatus`, `meta.requestId`, and `meta.creditsCharged`. Failed upstream lookups surface as typed outcomes — not an empty 200 that looks like a deleted pin.
The same API key covers the rest of the marketplace catalog (17 platforms, 137 endpoints), so a multi-network commerce or brand-monitoring pipeline does not need a second vendor for Pinterest. Write access, ads, and authenticated board management stay with Pinterest's official developer products.
What Pinterest data can you get?
- Keyword pin search for trend, assortment, and campaign discovery.
- Single pin detail by public URL — title, images, outbound link, saves.
- Profile board catalogs by Pinterest username (name, URL, pin count, cover).
- Board pin lists by board URL with cursor pagination.
- Shared `{ data, meta }` envelope with Instagram, TikTok, and the rest of the catalog.
- Public data only — secret boards and private pins are out of scope.
Pinterest API endpoints
Grouped by capability from the live API catalog. Open an endpoint page for parameters and examples — credit notes come from OpenAPI pricing extensions.
Lists & graphs
1Content
2Search & discovery
1How to call the Pinterest API
1. Create a key and smoke-test search
Sign up at Social Fetch and copy an `sfk_…` key. New accounts get 100 free credits. Start with `GET /v1/pinterest/search?query=…` against a real product or seasonal term so you see pin rows, cursors, and `meta.creditsCharged` before you wire batch jobs.
2. Follow the pin → board path
Hydrate a pin URL with `GET /v1/pinterest/pins`. For a brand or creator handle, call `GET /v1/pinterest/profiles/{handle}/boards`, then `GET /v1/pinterest/boards/pins` with each public board URL. Pass `x-api-key` on every call; paginate with the documented `cursor` when `data.page.hasMore` is true.
3. Join pins to commerce rows
Branch on `data.lookupStatus` before upserting. Store outbound `link` / `domain`, image URLs, save metrics, and board identity beside SKUs or creator IDs. Log `meta.requestId` on bad rows so support can trace the exact call.
How much does the Pinterest API cost?
Pinterest routes charge credits per completed lookup (including `not_found` when the request finished). Pin search, pin detail, profile boards, and board pins are documented at 1 credit each on successful completed calls — always trust `meta.creditsCharged` over a spreadsheet. Credits never expire on pay-as-you-go packs. Signup includes 100 free credits.
Social Fetch vs the official Pinterest API
Pinterest's official developer platform is for apps that publish, manage boards, run ads, or act with user OAuth. That is the right stack when you need write access or advertiser tools. It is the wrong stack when you only need public pin and board enrichment for arbitrary handles and URLs. Social Fetch looks up publicly visible pages the way a browser would, without OAuth to the pinner, and returns the same normalized envelope you already store for Instagram and TikTok.
Pinterest API FAQ
Is there a Pinterest scraper API that works without OAuth?
Yes. Social Fetch Pinterest routes read public pin and board data. You authenticate to Social Fetch with an API key (`x-api-key`). You do not OAuth as the Pinterest user whose public pins or boards you are fetching.
What Pinterest data does Social Fetch cover?
Four marketplace operations: keyword pin search (`GET /v1/pinterest/search`), single pin by URL (`GET /v1/pinterest/pins`), boards for a profile handle (`GET /v1/pinterest/profiles/{handle}/boards`), and pins on a board URL (`GET /v1/pinterest/boards/pins`). Exact paths, parameters, and examples live under `/docs/api` and on this hub's endpoint list.
Can I search Pinterest pins by keyword via API?
Yes. `GET /v1/pinterest/search` takes a required `query` string and returns matching public pins in the shared envelope. Pass `cursor` when `data.page.hasMore` is true to walk the next page. Optional `trim` shrinks the payload when you only need a subset of fields.
How do I get metadata for one Pinterest pin?
Call `GET /v1/pinterest/pins` with a public pin `url` (typically `https://www.pinterest.com/pin/{id}/`). Branch on `data.lookupStatus`, then read `data.pin` for title, description, image renditions, outbound link and domain, board summary, pinner, and metrics such as saves and repins.
How do I list boards for a Pinterest profile?
Use `GET /v1/pinterest/profiles/{handle}/boards` with the Pinterest username in the path. On a found lookup, `data.boards` can include name, url, pinCount, cover image, and related fields. Paginate with `cursor` when more pages exist. This route lists boards — not the pins inside them.
How do I pull all pins from a Pinterest board?
Pass the public board URL to `GET /v1/pinterest/boards/pins`. Walk pages with `cursor` until `hasMore` is false or your job hits a limit. Use this after you already have a board link from a profile boards list, a shared URL, or a watchlist.
How much does the Pinterest API cost on Social Fetch?
You buy credit packs (or spend the 100 free signup credits). Documented Pinterest lookups are typically 1 credit per successful completed request. Empty or `not_found` completed lookups still bill when the attempt finishes — check `meta.creditsCharged`. There is no required monthly subscription for pay-as-you-go packs.
Pinterest official API vs Social Fetch — which should I use?
Use Pinterest's official APIs when you need publishing, ads, or authenticated board management for users who authorize your app. Use Social Fetch when you need public pin search, pin detail, and board enrichment without building a Pinterest OAuth app — especially when those rows must sit next to Instagram and TikTok in one warehouse schema.
Are secret boards or private pins supported?
No. Only publicly visible profiles, pins, and boards. Secret boards, private pins, and deleted collections resolve as `not_found` (or equivalent typed outcomes) rather than inventing empty data.
Is scraping Pinterest data legal?
Social Fetch returns publicly visible data. You are responsible for how you use it under Pinterest's terms, applicable law, and your own compliance review. We do not give legal advice.
Start with Pinterest pin and board data
Create an account, spend the 100 free credits on a live pin search and a board pull, then buy a pack when the JSON fits your commerce or trend pipeline. Credits do not expire on pay-as-you-go packs.