Visual trend and inspiration research
Mit Pinterest-Endpunkten verwandelst du visual trend and inspiration research in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Turn Pinterest's public pins, boards, and profiles into structured JSON — keyword pin search, a pin's full detail, a user's boards and pins, a specific board's detail, and the "Ideas" category taxonomy with per-category feeds, all as normalized JSON. Credential-free.
Search Pinterest pins and get pin detail, boards, user profiles, and the Ideas category taxonomy as structured JSON.
Endpunkt-Familien
6
Dokumentierte Parameter
16
Beispiele
8
Live-Katalog-Snapshot
Aktive Endpunkte
8
Methoden
GET
Pflichtparameter
16
Schema-Referenzen
8
{
"platform": "Pinterest",
"endpoint": "pinterest-search",
"method": "GET",
"path": "/pinterest/search",
"auth": "apiKey"
}Use Cases
Search Pinterest pins and get pin detail, boards, user profiles, and the Ideas category taxonomy as structured JSON.
Mit Pinterest-Endpunkten verwandelst du visual trend and inspiration research in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Pinterest-Endpunkten verwandelst du creator and board monitoring in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Pinterest-Endpunkten verwandelst du content and category discovery in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Managed Execution
Jede Zahl unten stammt direkt aus dem Live-Pinterest-Endpunktkatalog — 8 Endpunkte, 16 dokumentierte Request-Parameter und 8 veröffentlichte Response-Schemas — demselben Katalog, gegen den auch Docs und Playground laufen.
8 documented Pinterest endpoints, grouped into 6 request families — User, Board and Categories, plus 3 more.
16 request parameters are documented across those Pinterest endpoints, 16 of them required — the full input contract is public before you write any integration code.
8 of the 8 Pinterest endpoints ship a recorded example response, and 8 carry a documented response schema — you can code against the real JSON before the first request.
Pinterest endpoints document their error responses (400, 404, 500 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
8 hosted MCP tools back the Pinterest endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Abdeckungskarte
/pinterest/user/{username}
/pinterest/board/{username}/{slug}
/pinterest/categories
/pinterest/ideas/{id}
/pinterest/pin/{id}
/pinterest/search
Endpunktkatalog
/pinterest/searchReturns public Pinterest pins matching a text query: title, description, image, board, and pinner for each result. Public data sourced from Pinterest's own web search.
Hinweise zur Response
- `image_url` is the largest reasonably-sized image Pinterest returned for the pin (preferring `736x`, falling back through `474x`/`orig`/`236x`/`170x`). - `title` can be empty — many pins carry only a description, not a separate title. - `domain`/`link` point at the pin's off-Pinterest source when the pin was saved from a website; pins uploaded directly by a user instead carry `"domain": "Uploaded by user"` with no `link`. - A missing `query` returns `400` before any upstream request is made.
MCP-Tool pinterest_search
/pinterest/pin/{id}Returns a single Pinterest pin's full detail: title, description, image, board, pinner, comment count, save count, and creation time. Public data sourced from Pinterest's own pin pages.
Hinweise zur Response
- `repin_count` is Pinterest's own save count for the pin; `comment_count` reflects public comments only. - An unrecognized `id` returns `404`. - A missing `id` returns `400` before any upstream request is made.
MCP-Tool pinterest_pin
/pinterest/board/{username}/{slug}Returns a Pinterest board's metadata (name, description, cover image, pin/follower counts, owner) plus a page of pins from that board. Public data sourced from Pinterest's own board pages.
Hinweise zur Response
- An unrecognized `username`/`slug` pair returns `404`. - A missing `username` or `slug` returns `400` before any upstream request is made.
MCP-Tool pinterest_board
/pinterest/user/{username}Returns a Pinterest user's public profile: display name, bio, website, avatar, and follower/following/pin/board counts. Public data sourced from Pinterest's own profile pages.
Hinweise zur Response
- An unrecognized `username` returns `404`. - A missing `username` returns `400` before any upstream request is made.
MCP-Tool pinterest_user
/pinterest/user/{username}/boardsReturns a page of a Pinterest user's own boards: name, description, cover image, and pin/follower counts for each. Public data sourced from Pinterest's own profile pages.
Hinweise zur Response
- `owner_username` on each board always matches the requested `username`. - Each board's `url` is usable directly as the `username`/`slug` path parameters to [`/pinterest/board/{username}/{slug}`](pinterest-board.md). - A missing `username` returns `400` before any upstream request is made.
MCP-Tool pinterest_user_boards
/pinterest/user/{username}/pinsReturns a page of a Pinterest user's own pins: title, description, image, board, and pinner for each. Public data sourced from Pinterest's own profile pages.
Hinweise zur Response
- `pinner_username` on each pin always matches the requested `username`. - A missing `username` returns `400` before any upstream request is made.
MCP-Tool pinterest_user_pins
/pinterest/categoriesReturns Pinterest's top-level "Ideas" category taxonomy (e.g. "Animals", "Home Decor", "Food And Drink"). Each entry's id is usable directly with GET /pinterest/ideas/{id}. Public data sourced from Pinterest's own ideas.pinterest.com-style category hub.
Hinweise zur Response
- Each entry's `id` is the value to pass as the `id` path parameter to [`/pinterest/ideas/{id}`](pinterest-idea.md). - This is Pinterest's full top-level list — currently 10 categories. It changes rarely; results are fetched live on every call, not cached client-side.
MCP-Tool pinterest_categories
/pinterest/ideas/{id}Returns one "Ideas" category's metadata (name, description, follower count) plus a page of pins from that category's feed. Public data sourced from Pinterest's own ideas category pages.
Hinweise zur Response
- `follower_count` reflects Pinterest's own follower count for the category as a whole, not the requester. - An unrecognized `id` returns `404`. - A missing `id` returns `400` before any upstream request is made.
MCP-Tool pinterest_idea
Verwandte APIs
Social & Creator Platforms
Build creator intelligence, video research, transcript, and audience-comment workflows without maintaining YouTube scrapers.
Social & Creator Platforms
Turn Twitch's public channel, stream, clip, and team data into structured JSON — live status and viewer counts, top games, clips, VODs, and team rosters — as normalized JSON. Credential-free.
Social & Creator Platforms
Track creator and video activity, discover sounds and LIVE streams, and study public ad creatives through documented TikTok API routes.
Unternehmensabdeckung
Pinterest, Inc. · PINS
Pinterest wird von Pinterest, Inc. (PINS) betrieben. Crawloras SEC-Endpunkte nutzen dieselbe CIK dieses Unternehmens, sodass Filings, Finanzdaten, Insider-Transaktionen und 13F-Beteiligungen mit demselben API-Key wie die Pinterest-Endpunkte oben abrufbar sind.
SEC-Filings & Finanzdaten-API →So scrapst du Pinterest
Crawlora's Pinterest endpoints return pin search, pin detail, boards, user profiles, and category feeds as normalized JSON with one API key — no Pinterest account required. A pull on 2026-10-27 listed 10 curated categories (Halloween first) and returned 21 pins for kitchen design, each with an opaque id.
Send a keyword to /pinterest/search for normalized pin results.
Pass a pin id to /pinterest/pin/{id}, or a username and board slug to /pinterest/board/{username}/{slug}.
Pass a username to /pinterest/user/{username} for their profile, or add /boards or /pins for their boards or own pins.
Use /pinterest/categories for the full list and /pinterest/ideas/{id} for a category's detail feed.
categories returned 10 entries with a numeric id and slug, such as 915794205972 for halloween. Ten entries is a short list, so treat it as seeds and use search for anything else.
search for kitchen design returned 21 pins with title, description, image URL and a long opaque id beginning e1_. Keep ids as strings, because they are not numbers.
Agent Skills
Installiere einen Crawlora Agent Skill, und dein Agent ruft Pinterest-Daten als JSON über die dokumentierte API ab, ohne einen Scraper zu schreiben. Diese Skills decken Pinterest ab:
Researches Pinterest profiles, boards, pins, ideas categories, and search results via the Crawlora API, returning clean JSON. Use when the user…
npx skills add github.com/Crawlora-org/crawlora-skills --skill pinterest-researchResearches public profiles, posts, trends, and Facebook Marketplace listings across Instagram, TikTok, Threads, Bluesky, X, Pinterest, LinkedIn…
npx skills add github.com/Crawlora-org/crawlora-skills --skill social-media-researchFAQ
Send a keyword to Crawlora's /pinterest/search endpoint and get normalized pin results as structured JSON — no Pinterest account required.
Yes — /pinterest/user/{username}/boards and /pinterest/user/{username}/pins return a user's boards and their own pins as structured JSON.
No Pinterest login or auth token is required from the caller — only your Crawlora API key.
Yes, but it's not self-serve. Pinterest's official API v5 requires a developer app, a Trial-access review (about one to two business days), and then a separate Standard/production-access application — including a video demo — that takes one to four weeks of manual review before you can call real endpoints outside the trial's public-hidden pins. Crawlora's Pinterest endpoints return pin search, pin detail, boards, and profiles as structured JSON with a single API key, no review process or waiting period.
Not in the search route on 2026-10-27: ids were long strings starting with e1_.