Search by keyword
Discover public pins with image metadata, descriptions, and destination links. Continue through results with source cursors.
PINTEREST API
Find the ideas.
Build what’s next.
Search public Pinterest pins and bring their images, creators, and board context into your application. Follow an idea from discovery to detail with four focused endpoints.
Live private service · production acceptance passed
WHAT’S ON THE MAP
The data you need.
The details that matter.
Get the pin details
Retrieve public pin metadata, available media fields, creator information, and source engagement counts.
Explore boards
List a user’s public boards, then retrieve the pins in a board with pagination and preserved source order.
YOUR FIRST REQUEST
Get to the
good data.
Start with a local worker and a service key. The examples use the current Pinterest contract.
GET
/v1/pinterest/searchSearch Pinterest pins
Discover public pins for a keyword. Retrieves one page with a requested page size of 25; Pinterest controls the actual result count and ranking. Pass cursor to continue. Full records retain available image, destination, board, author, counter and media fields. Trimmed pins contain id, url, description, created_at, pinner and images when supplied.
Request and response fieldsGET
/v1/pinterest/pinGet a Pinterest pin
Read a public pin’s page data without executing page scripts. Full responses expose Pinterest’s camelCase fields at the top level, preserving nested media and author data. imageSpec_orig aliases images_orig when needed. Trimmed fields: entityId, seoAltText, originPinner, pinner, imageSpec_orig, description, shareCount, nativeCreator, createdAt, repinCount and totalReactionCount. Counts are never guessed; missing required pin fields fail explicitly. cache_max_age is unsupported.
Request and response fieldsGET
/v1/pinterest/user/boardsGet a user’s boards
List one page of public boards, preserving order, source counts and nested metadata. Requests 25 boards. Cursor input is supported as an extension to the competitor’s documented request contract. Trimmed boards retain id, url, description, follower_count, pin_count, name, image_cover_hd_url and created_at when present. Pinterest does not supply every field for every board; absent timestamps and cover fields are not invented.
Request and response fieldsGET
/v1/pinterest/boardGet pins from a board
Resolve a public board and retrieve one page of its pins, requesting 25 items. Each returned pin’s board ID must match. All board sections are included where Pinterest supplies them. Pass cursor for the next page. Full records preserve source fields; trim=true uses the same compact pin fields as search. Media files and destination links are never downloaded.
Request and response fieldsQUICKSTART / LOCAL EXAMPLES
# Local worker · use your own service key
export BASE_URL="http://localhost:3014"
curl --get "$BASE_URL/v1/pinterest/search" \
-H "x-api-key: $PINTEREST_API_KEY" \
--data-urlencode "query=synthetic recipes"const baseUrl = "http://localhost:3014";
const url = new URL('/v1/pinterest/search', baseUrl);
url.searchParams.set("query", "synthetic recipes");
const response = await fetch(url, {
method: 'GET',
headers: {
'x-api-key': process.env.PINTEREST_API_KEY
}
});
const data = await response.json();
console.log(data);GET
/v1/pinterest/searchJSON responseExamples target local workers. Use the origin and credentials supplied for your service.
TAKE IT SOMEWHERE USEFUL
Made for what
you’re making.
Research visual ideas
Find public inspiration for your content planning and creative research workflows.
Organize discovery
Bring pins and their board context into searchable collections in your own application.
Connect ideas to sources
Use published destination links and creator metadata to enrich your research.
Which endpoints are available?
Search, pin details, user boards, and board pins are implemented. The dedicated worker is ready for local use; production deployment is pending.
Can I paginate or request less data?
Search, user boards, and board pins accept the cursor from the previous response. All four endpoints support trim=true for compact fields. Each call retrieves one page.
Is every pin or board included?
The API retrieves supported public data available without a Pinterest login. Restricted and unavailable content is reported explicitly. Coverage describes the returned page, and source fields may vary.
How do I connect?
Run the Pinterest worker and send its dedicated key in the x-api-key header. The API reference includes the local origin, parameters, responses, and limits.
Is this an official Pinterest API?
No. ScrapeAtlas is independent and is not affiliated with Pinterest. This endpoint retrieves supported publicly available data.