Pinterest Profile API

Look up public profile metadata using the required username query parameter. Use the Pinterest account username, not its display name; the recorded successful request used a username. Availability can depend on profile visibility and data availability. Observed success: HTTP 200 with status: ok, request_id, message: null and a nonempty data.user. Probe metadata confirmed data.user.id, username, full_name, pin_count, follower_count, following_count and last_pin_save_time. The observed id was the quoted decimal string "32088353503445352". Preserve its exact digits as a string for a numeric-ID follower request; do not convert it to a JavaScript number. If another response encodes an ID as an unquoted JSON integer, parse its raw token losslessly before string conversion. Observed not-found result: an HTTP 200 response contained status: error, request_id, a message explaining that no data was found and data.user: {}. Check the business status and profile content rather than interpreting transport success or an empty object as a valid zero-count account. Keep missing counts distinct from zero. Unverified documented examples additionally include about, first_name, board_count, created_at, domain_verified, eligible_profile_tabs, image_medium_url, image_xlarge_url, indexed, interest_following_count, is_ads_only_profile, is_gco_account, is_inspirational_merchant, is_partner, is_primary_website_verified, is_private_profile, is_verified_merchant, node_id, partner, profile_cover.url, seo_description, seo_title and type. These additional fields were not individually confirmed by the supplied probe metadata and may be unavailable. Documented error examples show detail for HTTP 400, detail[] entries with loc, msg and type for HTTP 422, and data.user, request_id and status for HTTP 500; those HTTP error cases were not probed. Follower and following totals are profile metadata, not relationship lists or proof of exhaustive enumeration. This response is a snapshot; any count history must come from your own repeated observations.

API Features

Confirmed username profile resolution Resolve an account username to observed public identity fields including data.user.id, username and full_name.

Public profile count snapshot Read observed pin_count, follower_count and following_count as snapshot values, leaving unavailable counts separate from zero.

Business-level not-found detection Recognize the observed HTTP 200 response with status: error, a no-data message and data.user: {} as a missing result rather than a valid account.

Lossless large-ID handoff Preserve the observed decimal-string ID unchanged for a numeric-ID follower lookup; use lossless token parsing only if another response returns an unquoted JSON integer ID.

Live API Demo

GET /api/project/pinterest-scraper/get-user-details

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/pinterest-scraper/get-user-details?key=<API_KEY>&username=example_user'

curl -X GET 'https://api.opendata-api.com/api/project/pinterest-scraper/get-user-details?key=<API_KEY>&username=example_user'

📢

Need Help?

If you encounter API issues or need other API requirements, please contact us.

Use Cases

Resolve a confirmed Pinterest username to an exact account ID before starting a separate numeric-ID follower lookup.
Maintain timestamped public profile snapshots for a creator shortlist, deriving any count-change history only from your own repeated captures.
Classify empty HTTP 200 profile results as business-level not-found outcomes instead of inserting fabricated zero-follower accounts into a directory.
Populate a profile review card with confirmed identity and count fields, displaying unavailable optional metadata distinctly from empty strings or numeric zero.

Frequently asked questions

What should I send in username?

Send the account's Pinterest username, not its display name. The parameter is required, and the successful probe used marthastewart. Replace the example_user default with the account you intend to inspect.

Can a missing profile still return HTTP 200?

Yes. The recorded nonexistent-username lookup returned HTTP 200 with status: error, a message that no data was found and data.user: {}. Check those response fields before treating the request as a successful profile lookup.

How do I preserve the user ID for a follower lookup?

The saved successful profile returned id as the quoted decimal string "32088353503445352". Keep that exact string for the follower route, not the profile username, and do not convert it to a JavaScript number. Only if another response uses an unquoted JSON integer ID should you parse the raw numeric token losslessly before string conversion; converting an already-rounded number cannot recover its digits.

Which profile fields were confirmed by the probe?

The successful metadata confirmed id, username, full_name, pin_count, follower_count, following_count and last_pin_save_time inside data.user, together with status, request_id and message. Other biography, image, website, flag and cover fields appear in documented examples but were not individually verified.

Do profile counts include complete lists or historical analytics?

No. Counts are snapshot metadata, not follower or following collections. Missing counts must remain distinct from zero, complete relationship enumeration is not established, and count history requires your own repeated snapshots.

Related operations

Guides

View Subscription Plans →

Get public Pinterest profile details by username