Pinterest reference
Pinterest API guide
Discover public pins, inspect an individual pin and use boards to retain collection context. A pin URL, its image URL and its outbound destination are different references.
Quickstart
Start with Pinterest
Discover public pins, inspect an individual pin and use boards to retain collection context. A pin URL, its image URL and its outbound destination are different references.
These requests use your API key and can spend credits. Check the current price on the endpoint page; each new page is a separate request. Later examples use illustrative identifiers: replace them with values from your earlier response.
1. Discover pins
Keep the query while following the returned cursor. Save pin URLs rather than using image URLs as pin identifiers. Parameters and current cost →
curl "https://www.monocrawl.com/v1/pinterest/search?query=small%20garden%20design" \ -H "x-api-key: mn_your_key_here"
2. Inspect a selected pin
Replace the example URL with a pin returned by search. Preserve the outbound source URL separately from the Pinterest citation. Parameters and current cost →
curl "https://www.monocrawl.com/v1/pinterest/pin?url=https%3A%2F%2Fwww.pinterest.com%2Fpin%2F1126955506790868948" \ -H "x-api-key: mn_your_key_here"
3. Read a known board
Supply a public board URL. Board collection is a separate read; follow only its returned continuation. Parameters and current cost →
curl "https://www.monocrawl.com/v1/pinterest/board?url=https%3A%2F%2Fwww.pinterest.com%2Flizmrodgers%2Fmoms-night%2F" \ -H "x-api-key: mn_your_key_here"
Filters and coverage
Choose filters with the source behavior in mind
| Control | Behavior and limits |
|---|---|
| Continuation | Search and board reads have their own cursor; never move a token between them. Endpoint reference → |
| References | Preserve the public pin URL, image URL and outbound source separately. Endpoint reference → |
Source availability, ordering and field coverage can change. Inspect warnings and partial-result metadata alongside the rows. See runnable workflows, metric semantics, computed fields and the pagination matrix.
Choose an endpoint
Match the operation to your task
| Your task | Endpoint | When to use it |
|---|---|---|
| Boards owned by a known account | boards | Use a handle; this is a board directory, not a merged feed of every pin. |
| One pin and its source link | pin | Keep image, pin and external destination URLs in separate fields. |
| Keyword discovery | search | Use a bounded collection budget; search ranking does not establish full coverage. |
Explore all documented operations by purpose below. Each endpoint reference contains its accepted parameters and current price.
Search and discovery
Operations
Each row is a registry operation: expand it for parameters, a curl built from the registry's own examples, and a Markdown copy of the whole entry. The badge on the right is the operation's state, read at request time — we publish all three rather than rounding up. Recorded proof is historical, not a guarantee of current availability.
- live · proven
- a real upstream response has been served through this API and recorded
- wired · unproven
- a real-data route is registered, but qualifying proof is absent; permission or capacity restrictions may apply
- sample · free
- no live upstream — /v1 refuses it, /sandbox returns a marked sample
Elsewhere
The same registry, other shapes
- Pinterest overview — supported data categories and use cases for this platform.
- Full endpoint reference — every platform on one page.
/openapi.jsonor/openapi.yaml— the machine-readable contract, for Postman, Insomnia or a client generator.GET /v1/utility/endpoints?platform=pinterest— the same rows to your code at runtime, for 0 credits.