# Pinterest API (/api/pinterest)

Pinterest pins, pin search, a user's boards and the pins on a board.

## When To Use This API [#when-to-use-this-api]

The Pinterest API is for agent workflows that need public, platform-native data without writing a custom collector for every task. Use it when a prompt needs evidence from live public records, when a Skill needs repeatable enrichment, or when product code needs the same contract an agent discovered through MCP.

This section lists 4 live Pinterest operations from the canonical OpenAPI spec. Each operation page documents the route, method, parameters, response envelope, pagination behavior when available, and the error vocabulary shared across UnifAPI.

- Find what people save for a product category, style or season with keyword pin search and save counts.
- Audit a brand's or creator's boards and the pins on each board for visual merchandising research.
- Trace a pin back to its source domain and link to see which sites drive visual discovery traffic.

## Agent Contract Notes [#agent-contract-notes]

Agents usually discover these endpoints with the hosted UnifAPI MCP server, inspect the operation schema, then call only the records needed for the current task. Developers can call the same endpoints over HTTP with an API key, which makes the path from exploratory agent run to production integration direct.

Every successful response uses a stable envelope with a request id, data payload, optional pagination cursor, and billing metadata. Errors use the same closed vocabulary across platforms, so retry logic, user-facing explanations, and cost reporting can stay consistent even when a workflow spans multiple public-data sources.

When you are choosing an operation, start from the public identifier the user already has: a profile username, post id, channel id, subreddit name, search term, or URL-derived slug. Prefer the narrowest endpoint that answers the question, then expand only when the agent needs more evidence. This keeps record usage predictable, makes citations easier to explain, and avoids turning a focused research task into an expensive crawl.

## Operations [#operations]

### Pins [#pins]

- [`GET /pinterest/pins/{id}`](/api/pinterest/pins/id/get) — Get a Pinterest pin — Returns one public Pinterest pin by id: image, title, description, link, board, pinner and save counts.

### Search [#search]

- [`GET /pinterest/search/pins`](/api/pinterest/search/pins/get) — Search Pinterest pins — Returns public Pinterest pins that match a keyword, with images, titles and links.

### Users [#users]

- [`GET /pinterest/users/{username}/boards/{board}/pins`](/api/pinterest/users/username/boards/board/pins/get) — List pins on a Pinterest board — Returns the public pins on a Pinterest board with images, titles, links and save counts.
- [`GET /pinterest/users/{username}/boards`](/api/pinterest/users/username/boards/get) — List a Pinterest user's boards — Returns the public boards of a Pinterest user with names, pin counts and cover images.