Pinterest Profile Scraper

Extract public Pinterest profile details and save one structured row per account. Pinterest Profile Scraper returns names, biographies, websites, follower and following counts, public verification indicators, content counters and available account dates.

Use known usernames or profile URLs to enrich brand and creator records, compare public accounts or maintain a source-linked profile directory.

At a glance	Details
📥 Input	Enter Pinterest usernames or canonical profile URLs such as https://www.pinterest.com/nissanusa/.
📤 Output	One profile per success row with the input source retained
📄 Pagination	Individual lookups; no result pagination
🔐 Login required	No
⚡ Processing	Up to 5 HTTP requests concurrently; up to 5 attempts for temporary failures
💾 Delivery	One Apify dataset view with individual records and complete nested JSON

What the Pinterest profile scraper collects 👤

The Actor reads a public profile and normalizes identity, links, counters and account indicators into one row. Verification and website status remain separate fields so different signals are not confused.

Data can include:

• Profile ID, username, name, URL, biography and avatar links
• Published website and domain fields
• Follower, following and content counters exposed by the profile
• Identity, merchant and domain verification indicators kept separately
• Available account dates and raw profile view/reach metrics

How to collect profile details from Pinterest 🚀

1. Enter one or more supported inputs.
2. Review the supported input format.
3. Start the Actor.
4. Open the Profiles dataset view and review success or failed rows.
5. Export the dataset or retrieve records from your application.

{
  "inputList": [
    "nissanusa"
  ]
}

Each input is a profile lookup, with no result pagination. Content counters are metadata; pins, followers and boards are not expanded into separate rows.

Pinterest profile details output fields 📦

Field	Type	Meaning
input	string	Original submitted input.
status	string	Whether this entity was successfully collected.
id	string or null	Id when supplied by Pinterest.
username	string or null	Username when supplied by Pinterest.
name	string or null	Name when supplied by Pinterest.
url	string or null	Url when supplied by Pinterest.
image_url	string or null	Image url when supplied by Pinterest.
image_large_url	string or null	Image large url when supplied by Pinterest.
is_verified	boolean or null	Is verified when supplied by Pinterest.
is_verified_merchant	boolean or null	Is verified merchant when supplied by Pinterest.
is_private	boolean or null	Is private when supplied by Pinterest.
follower_count	integer or null	Follower count when supplied by Pinterest.
first_name	string or null	First name when supplied by Pinterest.
last_name	string or null	Last name when supplied by Pinterest.
about	string or null	About when supplied by Pinterest.
website_url	string or null	Website url when supplied by Pinterest.
domain	string or null	Domain when supplied by Pinterest.
domain_verified	boolean or null	Domain verified when supplied by Pinterest.
is_primary_website_verified	boolean or null	Is primary website verified when supplied by Pinterest.
created_at	string or null	Created at when supplied by Pinterest.
last_pin_save_time	string or null	Last pin save time when supplied by Pinterest.
following_count	integer or null	Following count when supplied by Pinterest.
board_count	integer or null	Board count when supplied by Pinterest.
pin_count	integer or null	Pin count when supplied by Pinterest.
video_pin_count	integer or null	Video pin count when supplied by Pinterest.
story_pin_count	integer or null	Story pin count when supplied by Pinterest.
group_board_count	integer or null	Group board count when supplied by Pinterest.
profile_views	integer or null	Raw public profile_views field; no monthly-period interpretation is assumed.
profile_reach	integer or null	Raw public profile_reach field; no reporting period is assumed.
has_catalog	boolean or null	Has catalog when supplied by Pinterest.
has_published_pins	boolean or null	Has published pins when supplied by Pinterest.
seo_title	string or null	Seo title when supplied by Pinterest.
seo_description	string or null	Seo description when supplied by Pinterest.
cover_images	array or null	Cover images when supplied by Pinterest.
recent_pin_images	array or null	Recent pin images when supplied by Pinterest.

Nested field structure:

• cover_images[]: variant, url, width, height, dominant_color.
• recent_pin_images[]: variant, url, width, height, dominant_color.

The examples below use normalized public response data. Values are snapshots and may change; every top-level output field is included. Different media variants and nested objects remain inside the same row.

Complete representative success result:

{
  "input": "nissanusa",
  "status": "success",
  "id": "215610038318796125",
  "username": "nissanusa",
  "name": "Nissan",
  "url": "https://www.pinterest.com/nissanusa/",
  "image_url": "https://i.pinimg.com/75x75_RS/e7/7a/c1/e77ac1e3a2563ba7b8f6136923f1a26a.jpg",
  "image_large_url": "https://i.pinimg.com/280x280_RS/e7/7a/c1/e77ac1e3a2563ba7b8f6136923f1a26a.jpg",
  "is_verified": true,
  "is_verified_merchant": false,
  "is_private": false,
  "follower_count": 25530,
  "first_name": "Nissan",
  "last_name": "",
  "about": "EVs that electrify",
  "website_url": "http://www.nissanusa.com",
  "domain": "www.nissanusa.com",
  "domain_verified": true,
  "is_primary_website_verified": true,
  "created_at": "2012-02-29T20:02:33Z",
  "last_pin_save_time": "2026-09-08T18:21:51Z",
  "following_count": 168,
  "board_count": 14,
  "pin_count": 373,
  "video_pin_count": 0,
  "story_pin_count": 1,
  "group_board_count": 0,
  "profile_views": 10000001,
  "profile_reach": 7819499,
  "has_catalog": false,
  "has_published_pins": true,
  "seo_title": "Nissan (nissanusa) - Profile | Pinterest",
  "seo_description": "Nissan | EVs that electrify",
  "cover_images": [
    {
      "variant": "originals",
      "url": "https://i.pinimg.com/originals/ca/2b/2c/ca2b2c5a42721471e573068a52d41fd5.jpg",
      "width": 800,
      "height": 450,
      "dominant_color": null
    },
    {
      "variant": "750x",
      "url": "https://i.pinimg.com/736x/ca/2b/2c/ca2b2c5a42721471e573068a52d41fd5.jpg",
      "width": 736,
      "height": 414,
      "dominant_color": null
    },
    {
      "variant": "474x",
      "url": "https://i.pinimg.com/474x/ca/2b/2c/ca2b2c5a42721471e573068a52d41fd5.jpg",
      "width": 474,
      "height": 266,
      "dominant_color": null
    },
    {
      "variant": "1200x",
      "url": "https://i.pinimg.com/1200x/ca/2b/2c/ca2b2c5a42721471e573068a52d41fd5.jpg",
      "width": 800,
      "height": 450,
      "dominant_color": null
    }
  ],
  "recent_pin_images": []
}

Complete failed dataset item:

{
  "input": "invalid input",
  "status": "failed",
  "id": null,
  "username": null,
  "name": null,
  "url": null,
  "image_url": null,
  "image_large_url": null,
  "is_verified": null,
  "is_verified_merchant": null,
  "is_private": null,
  "follower_count": null,
  "first_name": null,
  "last_name": null,
  "about": null,
  "website_url": null,
  "domain": null,
  "domain_verified": null,
  "is_primary_website_verified": null,
  "created_at": null,
  "last_pin_save_time": null,
  "following_count": null,
  "board_count": null,
  "pin_count": null,
  "video_pin_count": null,
  "story_pin_count": null,
  "group_board_count": null,
  "profile_views": null,
  "profile_reach": null,
  "has_catalog": null,
  "has_published_pins": null,
  "seo_title": null,
  "seo_description": null,
  "cover_images": null,
  "recent_pin_images": null
}

A failed row preserves input, sets status to failed, and sets every other top-level field to null. The reason is written to the run log. Optional successful values remain null or empty when Pinterest omits them. The single dataset view exposes object fields as useful columns; arrays are kept in their parent row rather than expanded into additional rows or views.

Input and pagination settings ⚙️

Parameter	Type	Required	Default	Rules
inputList	array of strings	Yes	None	Enter Pinterest usernames or canonical profile URLs such as https://www.pinterest.com/nissanusa/.

Enter supported Pinterest profile URLs or usernames. Individual pin URLs, board URLs and keyword searches belong to their corresponding actors.

Use canonical HTTPS links on www.pinterest.com or pinterest.com. Country-specific hosts, shortened pin.it links and unsupported paths are not accepted. A leading @ is accepted for plain usernames; usernames are normalized.

Duplicate normalized inputs are processed once. A returned identifier is deduplicated within the pagination of one source input; the same object found under different source inputs retains each source relationship.

There is no result-page setting. Each unique target is looked up individually, and its nested fields stay in that single result row.

Pinterest profile details use cases 🎯

Brand and creator enrichment

Add public descriptions, websites, identifiers and audience counters to selected profile records. Use canonical URLs to keep sources easy to inspect.

Public account comparisons

Compare follower counts, content totals and verification indicators across chosen profiles. Keep their different meanings when building your own scoring method.

Profile change snapshots

Collect the same account inputs on a schedule and compare names, biographies, links or available counters in your own database.

Pricing and saved-result behavior 💰

Check the Actor’s Pricing tab for the active charging model and current rate. Store settings may change, so this README does not state an unverified fixed price or runtime.

Under dataset-item pricing:

• Each unique success result represents one profile for its source input.
• An invalid or unavailable input, an input with no accessible results, or a request that exhausts retries can produce a failed row.
• Retry attempts and supporting metadata requests do not create extra dataset rows by themselves.
• Nested media, author and source fields stay inside their parent result.
• A normal empty continuation after earlier successes creates no additional result row.
• Saved failed rows are not assumed to be free. Check the active pricing configuration for their treatment.

Larger page budgets and more inputs can produce more saved rows. Start with a small run and check actual usage before increasing the workload.

Pinterest profile details API 🔌

Replace $ACTOR_ID with the identifier shown in this Actor’s API tab and $APIFY_TOKEN with your Apify token.

curl -X POST "https://api.apify.com/v2/acts/$ACTOR_ID/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"inputList":["nissanusa"]}'

Download JSON, CSV, Excel, XML or other formats available in the Console, or retrieve the dataset through the Apify API. Schedules, webhooks and Apify integrations can connect results to Google Sheets, Make, Zapier, n8n, cloud storage or your own backend. These are connection options rather than integrations already configured by the Actor.

Reliability, retries, and public-data limits ⚠️

Collection uses pure HTTP with up to five concurrent requests. Invalid syntax and confirmed missing, removed or inaccessible targets stop without unnecessary retries. Temporary network or proxy failures, timeouts, blocking responses, malformed data, throttling and server errors are retried up to five total attempts per request.

Earlier successful pages remain saved when a later request fails. A normal end after previously saved results is not retried. An input that produces no accessible results can receive a failed row; this does not by itself prove the underlying account or collection does not exist. A later exhausted request can append a failed row while keeping earlier output.

Pinterest controls public availability, ranking, fields and pagination. Private, deleted, restricted or otherwise unavailable data can be omitted. Counts can change during collection, and media links can expire. Successful HTTP research confirms the supported request paths and pagination on tested sources, rather than future availability or exhaustive coverage.

profile_views and profile_reach are returned as source metrics; their time window is not established by this Actor. Do not assume they are exact monthly analytics. native_pin_count is not a guaranteed Created-pin total. Merchant, identity and domain verification are different signals. Private analytics and hidden contact information are not collected.

An invalid string within a valid input list does not stop other inputs. A configuration that fails validation, such as a non-string list item or an invalid page-count type, exits before requests start. Infrastructure errors such as startup failure, unavailable dataset storage or an unrecoverable result-save error can stop the whole run. A failed dataset save is not retried as a new scraping request.

Frequently asked questions ❓

Does it return monthly views?

It can return the source fields profile_views and profile_reach. Their precise reporting period is not established here, so the Actor does not relabel them as verified monthly analytics.

Does it export the profile’s pins or follower list?

No. This Actor exports profile metadata and counters. Use Profile Pins Scraper or Profile Boards Scraper for content discovery.

Are all verified profiles verified merchants?

No. Identity verification, merchant verification and website/domain verification are separate indicators and remain separate in the output.

Does it require Pinterest login or personal cookies?

No. The Actor uses HTTP requests from the public website. It does not require a Pinterest account, password or personal session cookie, and does not launch a browser.

What happens to invalid or unavailable inputs?

Invalid individual inputs are saved as failed rows without a source request. Confirmed unavailable targets stop without unnecessary retries. Temporary failures allow up to five total attempts; other inputs and previously saved results remain available.

Can I export results or schedule runs?

Yes. Download the default dataset in supported formats or retrieve it through the Apify API. Apify schedules and completion webhooks can connect repeated runs to your own workflow.

Support, responsible use, and related actors 🛟

For a reproducible issue, use the Actor’s Issues tab and provide the run ID, approximate time, safe public input, expected behavior and actual result. Include the selected mode or page count when applicable. Do not share access tokens, cookies or proxy credentials.

Use public data responsibly and follow applicable privacy, copyright, contractual and platform requirements before storing, analyzing or redistributing collected information.