Search for public Pinterest accounts
View all Pinterest Profiles, Followers & Pins endpoints →Search publicly discoverable Pinterest accounts with the required string query parameter username. Despite its name, this parameter accepts account-search text such as a username or partial name; the recorded probe used the multiword query martha stewart. Replace the illustrative example_user default with the intended search text. No page or cursor input is documented. Observed response: the recorded request returned HTTP 200 with status set to ok, request_id, message set to null and data.users containing 49 account records. The first result included username set to marthastewart, an id and full_name set to Martha Stewart; another candidate was MarthaWeddings. These observations establish candidate discovery for that query, not a fixed result count, guaranteed ranking, account ownership or an exhaustive directory. Preserve IDs as strings. Additional documented fields, not individually confirmed by the probe metadata: user records may contain image_small_url, image_medium_url, image_large_url, image_xlarge_url, board_count, pin_count, follower_count, last_pin_save_time, domain_verified, is_primary_website_verified and is_verified_merchant. The source example also includes contextual_pin_image_urls, pin_thumbnail_urls, recent_pin_images, node_id, type, blocked_by_me, explicitly_followed_by_me, is_ads_only_profile and is_default_image. Treat these as optional example fields, not a guaranteed schema; flags in this public search example are not evidence of an authenticated viewer's relationship with an account. Counts and verification flags, if present, are profile attributes rather than private analytics or independent proof of identity. The documentation illustrates HTTP 400 with a detail string, HTTP 422 with detail entries containing loc, msg and type, and HTTP 500 with status, request_id and data.users. No such error was recorded by the supplied probe, so these are documented examples rather than observed failure formats. Compare candidate usernames and available profile metadata rather than accepting the first match. A display name is not necessarily the username required by subsequent account requests. After a human or application selects a candidate, use its returned username for a separate profile lookup or pin request; search does not perform that enrichment automatically. Results may be ambiguous or incomplete, and this endpoint searches users rather than pins or boards.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/pinterest-scraper/search-users API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/pinterest-scraper/search-users?key=<API_KEY>&username=example_user'
Query Result
Use Cases
- Build a human-reviewed creator account picker that searches a supplied name, displays candidate usernames and records the selected account ID.
- Resolve similarly named brand accounts by reviewing multiple candidates before assigning a returned profile to an internal brand record.
- Maintain a content-research discovery queue with selected, ambiguous and no-candidate outcomes instead of treating the first search result as a verified match.
- Turn display-name-only contact notes into a reviewable list of possible Pinterest usernames, then run a separate profile lookup only for the chosen candidate.
Frequently asked questions
Can the username input contain a name with spaces?
Yes. The parameter is named username, but it is documented as search text such as a username or partial name. The recorded successful request used martha stewart. Replace the illustrative example_user default with your intended query.
Which account fields were verified in search results?
The observed response used status, request_id, message set to null and data.users. The first candidate contained username, id and full_name. Image URLs, profile counts, verification flags and other fields appear in the documentation example but were not individually confirmed by the probe metadata.
Does the first result identify the account I intended?
Not necessarily. The observed response included both marthastewart and MarthaWeddings. Compare usernames and available profile information before selecting a candidate; ranking and similar display names do not independently prove identity or ownership.
Will every matching account be returned, and can I paginate?
The recorded query returned 49 users, but no fixed result count or exhaustive coverage is established. This operation exposes no pagination input, so do not add an undocumented page or cursor parameter.
Should I use the display name or username for the next request?
Use the selected candidate's returned username when making a separate username-based profile or pin request. Preserve the account ID as a string for matching records. A full_name value is a display label and is not necessarily a valid account handle.
Can this search return pins or board collections?
No. This endpoint discovers user profiles through data.users. Request an account's available public pins separately after choosing the intended account.