Pinterest Following API: Accounts Followed by Username

Retrieve the available public accounts followed by a Pinterest profile. Supply the profile username in the query parameter named userid. Despite its name, this route takes a username, not the numeric userid used by the follower route. userid remains optional in the parameter contract, while the documented first-page workflow supplies a username. Omit bookmark for the first page. If a response supplies data.bookmark, keep the same username in userid and pass that token unchanged as bookmark. Stop on absent or repeated tokens and deduplicate returned IDs. A continuation token was observed, but another page was not requested, so pagination and exhaustive collection are not verified. Observed response: a successful recorded probe returned message: null, data.request_id, data.status set to ok, a nonempty data.bookmark and fifty data.followings[] records. Each record included node.username and node.id with cursor: null. Preserve IDs as strings; the observed collection-level bookmark, not those null record cursors, is the documented next-page input. Unverified documented examples additionally show node.__typename, entityId, fullName, imageMediumUrl, imageXlargeUrl, isPrivateProfile, type, board_count, follower_count, pin_count, domain_verified, is_default_image, is_verified_merchant, last_pin_save_time, pin_thumbnail_urls and recent_pin_images. Treat these example fields as illustrative rather than guaranteed. Documented error examples show detail for HTTP 400 and 500, and detail[] entries with loc, msg and type for HTTP 422; these errors were not observed in the successful probe. Following relationships describe accounts the target follows, not its followers, and do not establish endorsement, audience overlap or private interests.

API Features

Username-based following selection Pass a Pinterest username through userid on this route, keeping it distinct from the numeric ID accepted by the follower lookup.

Collection-level bookmark handoff Read data.bookmark for a possible next request while preserving the same username; the observed token was not tested on a second page.

Following account node extraction Normalize the observed data.followings[].node username and string id fields instead of reusing the follower response envelope.

Bounded interest-discovery records Use the fifty observed records as public research leads without claiming complete coverage, endorsement or shared audiences.

Live API Demo

GET /api/project/pinterest-scraper/list-user-following

API Response (JSON)

{}

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

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

📢

Need Help?

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

Use Cases

Find editorial research candidates among accounts a selected brand or creator publicly follows, without labeling the relationship as an endorsement.
Build a capped following-list collector that saves the original username and returned bookmark, deduplicates IDs and stops on missing or repeated tokens.
Create an outbound following view in a relationship explorer while keeping follower and following directions visibly separate.
Test request adapters to ensure this route sends a username in userid rather than accidentally reusing a numeric identifier from a follower request.

Frequently asked questions

Why does userid take a username on the following endpoint?

That is this route's documented input format. Supply the Pinterest username in userid; the successful probe used marthastewart. Do not reuse the numeric userid expected by the follower endpoint.

How should bookmark be used for the next page?

Omit bookmark initially. When data.bookmark is returned, preserve the same username and pass that token unchanged. Stop when it is absent or repeats. A nonempty bookmark was observed, but the next page was not tested.

Should I use the cursor inside each following record?

The recorded records had cursor: null. The documented continuation input for this route is the collection-level data.bookmark, not the per-record cursor.

What did the successful following probe confirm?

It confirmed message: null, data.request_id, data.status of ok, a nonempty data.bookmark and fifty data.followings[] records with node.username and node.id. Additional profile metrics and images appear only in unverified documented examples.

Does the following list prove endorsement or complete interest coverage?

No. It identifies returned public accounts the target follows, not its followers, endorsements or private interests. Neither exhaustive enumeration nor audience overlap was established by the recorded probe.

Related operations

Guides

View Subscription Plans →

List accounts followed by a Pinterest username