Pinterest Profile Scraper

Extract public Pinterest profile data from usernames or profile URLs: follower and following counts, pin and board totals, bios, websites, verification signals, and optional board and pin previews. Use the results to compare creators and brands or prepare content-research snapshots, then export JSON, CSV, or Excel from Apify.

Only information exposed on the public profile page is available. Board and pin arrays are previews, not a complete history, and some profiles return none.

Quick start

1. Add a public Pinterest username or profile URL.
2. Start with one profile and small preview limits.
3. Click Start, then open the dataset and export the results.

{
  "usernames": ["pinterest"],
  "includeBoards": true,
  "maxBoardsPerProfile": 3,
  "includePins": true,
  "maxPinsPerProfile": 4,
  "proxyConfiguration": { "useApifyProxy": false }
}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose a public example to see its settings before starting a run:

• Scrape Pinterest profiles by username list
• Extract recent Pinterest pin previews from a profile
• Extract Pinterest board previews from a profile

What you get

One successful profile row with available account identity, public counters, bio and website. Optional boards and pins are nested previews rather than separate result rows or complete histories. Missing counts stay null, empty arrays can mean disabled or unavailable previews, and absent verification signals become false without proving unverified status.

Who is it for?

• Creator researchers reviewing public account signals before shortlisting.
• Brand analysts retaining their own dated profile snapshots.
• Content planners inspecting available board names and pin references.
• Data teams joining known profiles and nested previews in their own systems.

How you can use the data

• Review the existing Pinterest account sample. Look up pinterest with three boards and four pins at most and explicit direct access. Keep username, profileUrl and source counters without assuming every preview slot is populated.
• Collect lighter profile snapshots. Disable both preview options when follower, following, board and pin totals are enough. Keep scrapedAt with null counts rather than interpreting missing monthly views as zero.
• Prepare topic notes from exposed previews. Retain board names and descriptions with pin links, image references and available board attribution. Preview limits do not fetch additional pages or guarantee newest-first order. Topic analysis or content planning happens in your destination.
• Compare or continue a batch yourself. Join usernames and extraction times across datasets for your own growth or brand comparisons. If a cutoff produces PENDING_PROFILES, supply that record in a new run and choose preview settings again. Completed profiles are not automatically loaded, and the Actor does not calculate growth, rank creators or send alerts.

Input settings

Supply at least one of profileUrls, usernames, or a valid resumeCheckpoint. Targets are combined and deduplicated by username, with at most 100 unique profiles per run. The example values shown in the form are prefills, not required API defaults.

Setting / JSON key	Default	Purpose
Pinterest profile URLs / profileUrls	None	HTTPS Pinterest profile URLs, as strings or objects with a url key.
Pinterest usernames / usernames	None	Usernames, @handles, or supported profile URLs.
Include board previews / includeBoards	true	Include available nested boards.
Maximum boards / maxBoardsPerProfile	10	Store up to 0–100 board previews per profile.
Include pin previews / includePins	true	Include available nested pins.
Maximum pins / maxPinsPerProfile	20	Store up to 0–100 pin previews per profile.
Proxy configuration / proxyConfiguration	{"useApifyProxy":false} in the form	Choose no proxy, Apify Proxy, or your own proxy settings. See field help.
Maximum retries / maxRetries	3	Limit retries for temporary request failures. 0–6.
Maximum concurrency / maxConcurrency	8	Process 1–20 profiles in parallel.
Runtime safety limit / runtimeSafetySecs	240	Stop starting new work after 30–270 seconds.
Resume checkpoint / resumeCheckpoint	None	Add pending targets from a prior PENDING_PROFILES record.

Lower preview limits shorten rows. They do not increase what Pinterest exposes. To return profile counts without nested previews, set both include options to false.

Example inputs

Use the Quick start input as a small first run. Adjust the fields described above for your own data.

Output data

One dataset row is saved for each successfully extracted profile. Optional strings and counters may be null. Disabled or unavailable preview arrays are empty. Missing verification signals resolve to false, not proof that an account is unverified.

Illustrative shape only, not a measured profile or live result:

{
  "profileUrl": "https://www.pinterest.com/example/",
  "username": "example",
  "fullName": null,
  "profileDescription": null,
  "website": null,
  "followerCount": null,
  "followingCount": null,
  "pinCount": null,
  "boardCount": null,
  "monthlyViews": null,
  "verified": false,
  "boards": [],
  "recentPins": [],
  "scrapedAt": "2026-10-25T00:00:00.000Z"
}

Fields	Meaning
id, nodeId, profileUrl, username	Available Pinterest identifiers and canonical account URL.
fullName, profileDescription, website	Display name, bio, and linked website.
imageUrl, coverImageUrl	Profile and cover image URLs, when available.
followerCount, followingCount, pinCount, boardCount, monthlyViews	Public counters. Missing values remain null.
verified, verifiedMerchant, domainVerified, partner	Combined verification signal and individual public account flags.
accountType, indexed, location, country, createdAt	Available account type, indexing flag, location, country, and creation date.
boards	Board previews: id, name, url, description, followerCount, pinCount, coverImageUrl.
recentPins	Pin previews: id, title, description, pinUrl, link, imageUrl, boardName, boardUrl, createdAt, repinCount, commentCount.
scrapedAt	Time the profile was extracted.

The dataset schema retains a legacy error field. Current failures are reported through RUN_SUMMARY, not dataset error rows. Use JSON export to preserve nested previews.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

The start event is charged once after validation. The item event applies to each saved profile row, including its available nested board and pin previews without separate preview result events. Failed profiles do not create paid item rows, while a run with no saved profiles can still incur start.

Start with one account and small preview caps. See the Pricing tab for current rates and discounts.

Tips for best results

• Begin with one known public username. Form examples are prefills rather than required API defaults.
• Turn off previews for a lighter account snapshot. Smaller preview caps do not expose additional content.
• Keep null counters unknown. Public monthly-view or engagement fields can be unavailable.
• Use JSON when retaining nested boards and pins. They remain inside the profile row.
• Select preview options again for a continuation. A checkpoint adds targets rather than restoring settings.

Limits and caveats

Only public Pinterest profile information is supported without login. Private boards, account-only analytics and complete pin archives are unavailable. Temporary limits, restrictions, missing targets and page changes can prevent collection. An inaccessible response does not prove privacy or deletion.

Profile URLs, usernames and valid checkpoint targets combine and deduplicate by username, with at most one hundred unique profiles per run. Form examples are not required API defaults. Board and pin arrays are exposed previews rather than complete histories, extra-page requests or newest-first samples. Smaller caps limit stored previews rather than increasing availability.

Public strings and counters can be null. Disabled or unavailable previews are empty arrays. Missing verification flags become false rather than proving an account is unverified. Legacy dataset error is retained in the schema, but current failures are reported through RUN_SUMMARY rather than dataset error rows.

Completed profiles remain available in partial batches. RUN_SUMMARY records requested, saved, failed and pending counts and failure reasons, using PARTIAL for mixed outcomes. If every profile fails, the run fails. A successful or partial batch does not establish that all targets completed.

At the runtime cutoff, PENDING_PROFILES can record unfinished targets. Supply that record as resumeCheckpoint in a new run and choose preview settings again: checkpoint data does not restore them or load completed targets. Optional summary or checkpoint storage can fail independently of saved rows, so consult the run log if absent. Growth calculations, sorting, comparison and alerts remain your own workflow.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~pinterest-profile-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "usernames": [
    "pinterest"
  ],
  "includeBoards": true,
  "maxBoardsPerProfile": 3,
  "includePins": true,
  "maxPinsPerProfile": 4,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
JSON

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/pinterest-profile-scraper').call({
  "usernames": [
    "pinterest"
  ],
  "includeBoards": true,
  "maxBoardsPerProfile": 3,
  "includePins": true,
  "maxPinsPerProfile": 4,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/pinterest-profile-scraper').call(run_input={'usernames': ['pinterest'], 'includeBoards': True, 'maxBoardsPerProfile': 3, 'includePins': True, 'maxPinsPerProfile': 4, 'proxyConfiguration': {'useApifyProxy': False}})
print(client.dataset(run['defaultDatasetId']).list_items().items)

API and integrations notes

Example request: “Look up the Pinterest username pinterest with both preview options disabled and proxyConfiguration.useApifyProxy set to false. Retrieve the dataset and report available follower and board counts, leaving missing values unknown.”

MCP and AI agents

You can ask your AI assistant to collect data with Pinterest Profile Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Pinterest Profile Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/pinterest-profile-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Pinterest Profile Scraper by Fetch Cat, or give it the identifier fetch_cat/pinterest-profile-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s Pinterest Profile Scraper to retrieve username pinterest with up to 3 board previews and 4 pin previews and explicit direct access. Keep available counts and source links without claiming a complete board or pin archive.”
• “Collect the public profile for pinterest with both board and pin previews disabled and explicit direct access. Keep follower and board counts with collection time, leaving missing values unknown for my own snapshot comparison.”
• “Retrieve pinterest with board previews enabled and capped at 2, pin previews disabled and explicit direct access. Keep available board names, descriptions and links for my own topic notes without ranking creators or claiming newest-first coverage.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Can I export Pinterest profiles to CSV or JSON?

Yes. Export the saved dataset from Apify. CSV is convenient for profile-level fields. JSON preserves nested board and pin previews.

Is this a Pinterest profile API alternative?

It provides an Apify API for public profile extraction, not an official Pinterest API. It needs no Pinterest account and does not provide private analytics or guarantee access to every profile.

Why are monthly views, boards, or recent pins missing?

Pinterest does not expose every field or preview on every public profile. Limits cap the available previews. They do not fetch additional pages or impose a newest-first sort.

Can I resume an unfinished batch?

Yes, when PENDING_PROFILES is available. Supply it as resumeCheckpoint and choose your desired preview options again. Already completed targets are not automatically loaded from a previous run.

Related Actors

• Pinterest Search Scraper — Discover pins by keyword.
• Bilibili Video Search Scraper — Extend content-topic research to public videos.
• TikTok Profile Scraper — Compare public account data on TikTok.
• Facebook Pages Scraper — Collect public Page details and visible post links.
• Bluesky Profile Feed Scraper — Explore public profiles and posts on Bluesky.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥