Pinterest Pin API
Pass a public Pinterest pin URL and get title, images, outbound link, board, and engagement in the shared Social Fetch JSON envelope.
GET /v1/pinterest/pins1 credit Failed requests are free
About this endpoint
GET /v1/pinterest/pins takes a public pin url query param. On a completed lookup, branch on data.lookupStatus first — found or not_found. When status is found, read data.pin: id, canonical url, title, description, altText, outbound link and domain, dominantColor, createdAt, image sizes (orig through size736), pinner and originPinner, board summary, visualAnnotations, and metrics (saves, comments, reactions, repins, shares). Optional trim=true shrinks the payload.
This route is one pin by URL. To discover pins by keyword use GET /v1/pinterest/search. To page pins on a board use GET /v1/pinterest/boards/pins. Pricing is 1 credit per successful completed lookup. Confirm with meta.creditsCharged.
Pinterest Pin API FAQ
How do I get a Pinterest pin by URL via API?
Call GET /v1/pinterest/pins with your Social Fetch API key (x-api-key) and a public pin url query param. Read data.lookupStatus, then data.pin when status is found. See the API docs for parameters and examples.
How much does the Pinterest Pin API cost?
Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged — that field is the billing source of truth.
What URL formats does the Pinterest Pin API accept?
Public Pinterest pin links, typically https://www.pinterest.com/pin/{id}/. Private, deleted, or otherwise unavailable pins resolve as not_found. Pass the link as the url query param.
What fields are in the Pinterest pin response?
When lookupStatus is found, data.pin includes id, url, title, description, altText, outbound link and domain, dominantColor, createdAt, image renditions, pinner and originPinner snapshots, board summary, visualAnnotations, and metrics (saves, comments, reactions, repins, shares). Fields may be null when Pinterest does not expose them.
What does not_found mean for a Pinterest pin lookup?
lookupStatus of not_found means the pin did not resolve to a public payload. data.pin is null. HTTP 200 still means the request finished; keep meta.requestId if you need support on that row.
Pin detail vs search vs board pins?
Use GET /v1/pinterest/pins when you already have a pin URL and need metadata. Use GET /v1/pinterest/search to find pins by query. Use GET /v1/pinterest/boards/pins to list pins on a public board. They are separate paths on the Pinterest hub.
Does this include secret or private boards?
No. Only publicly visible pins. Secret boards and private content are out of scope for this route.