Pinterest API

It is a REST API that returns public Pinterest data as structured JSON. Six POST endpoints cover profiles, keyword search, single pin detail, a profile's boards, a single board with its pins, and Pinterest save counts for a list of URLs. You authenticate with a Scavio API key and never handle Pinterest credentials.

Yes, and this is the endpoint that sets Scavio apart. The profile endpoint takes a username and returns follower, following, pin, board and group-board counts, the about text, website and domain-verification status, plus partner and merchant flags and the account creation date. Account-level profile data like this is something competing Pinterest APIs generally do not sell — several list it as planned rather than live. On Scavio it is one call and one credit.

The search and board responses include a cursor field. Pass that value back in your next request to get the following page of pins; keep going until the cursor comes back null, which means there are no more results. The board endpoint also accepts a page_size between 1 and 50 so you can tune how many pins come back per call. User-boards may return every board in a single page when the list is short.

The pin endpoint resolves a pin from a full Pinterest URL on any Pinterest domain, a bare numeric pin id, or a pin.it short link. It returns the title, description, alt text, images at four sizes, video url when the pin is a video, save and repin counts, share and comment counts, the dominant color and the board and pinner behind it.

Profile, search, pin, user-boards and board each cost 1 credit per successful call. URL stats cost 1 credit for up to 5 URLs and 2 credits for 6 to 10 URLs in one call, and that cost is charged before the request runs so you are never surprised. New accounts get 50 free credits on signup, one time, with no card required. Paid plans start at $30 per month for 7,000 credits.

The url-stats endpoint reports how many times each page has been pinned across Pinterest — a distribution signal for up to ten URLs at once. These counts are matched on the exact URL string, so a page that is pinned under a different URL form will read lower, and some domains report zero even when they clearly have activity. Treat the number as a directional signal for content that is being saved, not as an audited metric.

No. Pinterest's own developer API requires registering an app, going through review, and issuing per-user OAuth tokens, and it is oriented around accounts that have authorised your app rather than arbitrary public profiles and boards. Scavio needs none of that: sign up, take the key, POST a username or URL.

No. Only data Pinterest makes publicly available is returned. A private profile or a secret board is not accessible, and the API never authenticates as a Pinterest user. The profile response includes an is_private_profile flag so you can see when an account is private.

Anyone who needs public Pinterest data as structured JSON rather than a browser tab. Developers embedding it in a product; AI agent builders wiring Pinterest in as an MCP or SDK tool; automation engineers running it inside n8n, Zapier or Make; marketing and trend teams tracking creators, boards and what is being saved; and researchers building image or interest datasets. The API is identical for all of them — what changes is which of the six endpoints you call.

Official Python (pip install scavio) and JavaScript/TypeScript (npm i scavio) SDKs, a remote MCP server at mcp.scavio.dev for AI agents, and an n8n community node. Any language can call the REST endpoints directly with an HTTP client — every one is a POST that takes JSON and returns JSON.

Scavio returns publicly available data and does not access private content or authenticate as a user. You remain responsible for how you use the data, including compliance with Pinterest's terms and with privacy law such as GDPR where personal data is involved. Talk to your own counsel for your specific use case.