List public Pinterest followers by numeric user ID
View all Pinterest Profiles, Followers & Pins endpoints →Retrieve a bounded snapshot of accounts that follow a Pinterest profile. For the initial request, pass the numeric Pinterest user ID as the string userid; a username is not a substitute. The query parameters are individually optional in the contract, but the documented starting request uses userid. For continuation, use only a node_id and cursor actually supplied by a response, and omit userid, including its default, because userid takes precedence. Do not invent continuation values. Stop when no usable pair is available or a token repeats. Observed response: a successful recorded probe returned message: null, data.request_id and ten data.followers[] records. Each record included a node with username, fullName, entityId and id, plus cursor: null. Keep identifiers as strings. No usable continuation was observed, so these records do not establish a complete follower export. Unverified documented examples additionally show node.__typename, imageMediumUrl, imageXlargeUrl, isPrivateProfile and status. These extra fields are illustrative, not guaranteed by the probe evidence. Documented error examples show detail and headers.Error for HTTP 400, a detail[] array containing loc, msg and type for HTTP 422, and data.followers, request_id and status for HTTP 500; these error shapes were not observed in the recorded successful probe. This read lists followers, not the accounts the target follows, and does not provide private audience analytics.
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/list-user-followers API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/pinterest-scraper/list-user-followers?key=<API_KEY>&userid=125186202050495625'
Query Result
Use Cases
- Create a timestamped follower relationship table from returned node IDs and usernames, retaining string identifiers and an explicit partial-coverage label.
- Prepare a bounded follower CSV for consent-aware manual audience research without representing the rows as the entire audience.
- Implement a follower continuation diagnostic that stops on missing node-and-cursor information or repeated tokens instead of fabricating another page.
- Compare saved follower snapshots for observed arrivals and departures while warning that incomplete coverage cannot prove an unfollow.
Frequently asked questions
Should userid contain a Pinterest username or a numeric ID?
Use the numeric Pinterest user ID as a string for the initial follower request. The successful probe used that form. Obtain the ID from a confirmed profile lookup rather than inserting a username.
How do I request another page of followers?
Continue only if a response supplies usable node_id and cursor values. Send those values and omit userid, including its default, because userid takes precedence. Stop on missing continuation information or repeated tokens; the probe did not establish working pagination.
Does a successful response contain every follower?
No completeness guarantee is established. The recorded success contained ten follower records with null cursors and no usable continuation. Label the result as a bounded snapshot rather than a complete export.
Which follower fields were actually observed?
Probe metadata confirmed message: null, data.request_id, data.followers[] and node fields username, fullName, entityId and id, with null record cursors. Image URLs, privacy flags and status appear in documented examples but were not separately verified by that metadata.
Is this the same relationship as the following list?
No. Followers are accounts that follow the target profile. The following list describes accounts the target follows and uses a separate endpoint and input format.