Skip to main content
Pinto is an unofficial TypeScript/JavaScript API for reading public Pinterest data: pins, boards, profiles, and search results.
Status: pre-release. Pinto is under active development and the public API may still change before 1.0.0. The read surface (getPin, getUser, getBoard, search, media downloads) is stable and covered by a live test suite. Pin your version in production.

​
Why Pinto

No browser required

Pinto talks to Pinterest’s public widget and resource endpoints directly over fetch. No Selenium, no Puppeteer, no Chromium.

Read-only by design

It fetches public pins, boards, profiles, and search results. It never posts, follows, or messages on your behalf.

Anonymous out of the box

Each session gets a stable, randomly selected browser profile so every client reads as a distinct device. See Device fingerprinting.

Built to scale

A session pool, shared cache, global rate limiter, and coalescing gateway. See Scaling.
Pinto has a fully typed public surface and ships both ESM and CJS builds.

​
Under the hood

Pinto is built around Pinth, its protocol layer. Pinth knows Pinterest’s URLs, widget and resource endpoints, browser headers, device profiles, and response formats. The rest of Pinto sits on top of it: a Client for throttled, retried requests, Vault for session cookies, Harvest for turning raw JSON into typed objects, and Scale for running many sessions.

How Pinto works

A full walkthrough of Pinth and every layer, and what happens on each request.

​
Disclaimer

Pinto is not affiliated, associated, authorized, endorsed by, or in any way officially connected with Pinterest or any of its subsidiaries or affiliates. “Pinterest” and related names, marks, emblems, and images are registered trademarks of their respective holders. Pinto is a read-only research tool. It is not intended for spam, bulk abuse, or circumventing Pinterest’s protections at scale. Use it fairly and in line with Pinterest’s Terms of Service.

Quickstart

Install Pinto and read your first pin.