Pinterest scraper API

Yes. /v1/pinterest/search returns pins for a query, page by page. Add include=engagement to fill in engagement counts on each row.

Yes. /v1/pinterest/board returns a board's pins, and /v1/pinterest/user/boards lists an account's boards.

A single pin is 10 credits. Search is metered: it quotes a range and charges what the page read. Calls that fail or find nothing are free.

Yes. /v1/pinterest/trends returns the Pinterest Trends list for one country: ranked search terms with a relative search index, as growing, seasonal, top_monthly or top_yearly tables. It is 100 credits a call and needs no keyword to start from.

/v1/pinterest/url-stats takes up to 10 URLs and returns how many times each has been saved through the Pinterest Save Button. Pass each URL exactly as it is used: http and https, or a trailing slash, count as different URLs.

/v1/pinterest/board returns about 15 pins a page with save, comment and share counts, and a cursor for the rest. Add include=engagement for each pin's date and reaction count.

No. There is no Pinterest app, OAuth flow or review. One API key in the x-api-key header works for Pinterest and the other 24 platforms.

Yes. Your first 10 calls priced at 100 credits or less are free, and the free plan includes 500 credits every month. No credit card is needed to get a key.

60 requests a minute and 10 requests in flight at once, per API key. Going over either returns a 429 with a Retry-After header, and a rejected request costs nothing. There is no daily quota: past those two limits, your credit balance is what bounds volume.

List endpoints return rows in data.items and a pagination object with next_cursor and has_more. Send next_cursor back unchanged as the cursor parameter for the next page, and stop when has_more is false. A handful of endpoints page with their own parameter instead; their reference pages name it.

No. A call that errors or finds nothing costs 0 credits. A live fetch costs the endpoint's price, or for a metered endpoint what it actually read. An answer served from the shared cache costs 2 credits. Repeating a call is charged like the first time, because it can return newer data.

A call fetches live unless a recent copy is in the shared cache, and every response says which with the cached field; a cached answer costs 2 credits. Add fresh=1 or send Cache-Control: no-cache to skip the cache; that call is charged at the normal price.

Collecting publicly available data is generally treated differently from accessing private data, but the answer depends on your jurisdiction, Pinterest's terms and what you do with personal data afterwards. The API reads public data only. Talk to a lawyer for anything commercial.