SocialBlade Creator Stats Scraper

Track public creator growth without manually copying numbers from SocialBlade.

SocialBlade Creator Stats Scraper turns creator profile pages into analysis-ready JSON, CSV, Excel, or API output. Supply SocialBlade URLs or platform and username pairs and receive one structured record per creator.

It supports YouTube, TikTok, Instagram, Twitch, and Facebook creator profiles.

Each successful record can include audience size, views, uploads, SocialBlade grade, global and category ranks, profile metadata, linked social accounts, and optional 15-day history.

What does SocialBlade Creator Stats Scraper do?

The Actor visits public SocialBlade creator profiles and extracts the structured profile state used by the page.

Use it to:

• 📈 snapshot subscriber or follower counts;
• 🏆 compare SocialBlade grades and ranks;
• 🎬 collect views and upload totals;
• 🌍 segment creators by country and category;
• 🔗 discover linked public social profiles;
• 🗓️ retain the available 15-day daily history;
• 🔁 run the same watchlist on a schedule.

The Actor returns source facts rather than modeled sponsorship or earnings claims.

Who is it for?

Influencer agencies

Refresh a client or prospect watchlist before campaign planning and reporting.

Brand partnership teams

Compare potential partners by audience, momentum, country, category, and rank.

Talent managers

Monitor creators across platforms and preserve snapshots for negotiations.

Creator economy analysts

Build repeatable datasets for growth, ranking, and market research.

Data and automation teams

Feed normalized creator statistics into warehouses, dashboards, alerts, and enrichment workflows.

Why use this SocialBlade scraper?

Manual profile checks do not scale and are difficult to reproduce.

This Actor provides:

• one stable record shape across five platforms;
• URL input and structured platform/username input;
• canonical URL deduplication;
• typed success and error records;
• nested history that stays attached to its creator;
• conservative request concurrency;
• browser-like HTTP requests with proxy fallback;
• pay-per-successful-profile charging.

Supported creator platforms

Platform	Structured lookup	Example SocialBlade route
YouTube	{ "platform": "youtube", "username": "mrbeast" }	/youtube/handle/mrbeast
TikTok	{ "platform": "tiktok", "username": "creator" }	/tiktok/user/creator
Instagram	{ "platform": "instagram", "username": "creator" }	/instagram/user/creator
Twitch	{ "platform": "twitch", "username": "ninja" }	/twitch/user/ninja
Facebook	{ "platform": "facebook", "username": "page" }	/facebook/page/page

YouTube channel IDs beginning with UC are converted to SocialBlade channel routes.

What data can you extract?

Field	Type	Description
status	string	ok or error
platform	string	YouTube, TikTok, Instagram, Twitch, or Facebook
username	string	Resolved public creator identifier
profileId	string	Source platform or SocialBlade creator ID
displayName	string	Public creator or channel name
profileUrl	string	Canonical SocialBlade profile URL
avatarUrl	string	Public avatar image URL
bannerUrl	string	Public banner image URL when available
description	string	Public profile description
country	string	Country code when available
category	string	Creator or channel category
createdAt	string	Source account creation date when exposed
audience	number	Subscribers or followers
views	number	Total view count when supported
uploads	number	Video, upload, or post count when supported
grade	string	SocialBlade grade
ranks	object	SocialBlade, audience, views, country, and category ranks
linkedSocials	array	Linked public social profiles
history	array	Available daily audience, views, and upload snapshots
scrapedAt	string	UTC extraction time

Fields unavailable for a particular platform remain absent or null rather than being guessed.

How to scrape creator statistics

1. Open the Actor input page.
2. Add one or more SocialBlade profile URLs.
3. Alternatively, add platform and username pairs.
4. Keep Include 15-day history enabled for trend snapshots.
5. Set a small maximum profile count for your first run.
6. Start the Actor.
7. Export the dataset or connect it to your workflow.

A successful profile is charged only after useful source data is extracted.

Input example: profile URLs

{
  "profileUrls": [
    { "url": "https://socialblade.com/youtube/handle/mrbeast" },
    { "url": "https://socialblade.com/twitch/user/ninja" }
  ],
  "includeHistory": true,
  "maxProfiles": 2,
  "maxConcurrency": 2
}

SocialBlade URLs must use a supported creator profile route.

Input example: platform and username

{
  "profiles": [
    { "platform": "youtube", "username": "mrbeast" },
    { "platform": "twitch", "username": "ninja" }
  ],
  "includeHistory": true,
  "maxProfiles": 2
}

The Actor deduplicates targets that resolve to the same canonical SocialBlade URL.

Output example

{
  "status": "ok",
  "input": "youtube:mrbeast",
  "platform": "youtube",
  "username": "mrbeast",
  "profileId": "UCX6OQ3DkcsbYNE6H8uQQuVA",
  "displayName": "MrBeast",
  "profileUrl": "https://socialblade.com/youtube/handle/mrbeast",
  "country": "US",
  "category": "entertainment",
  "audience": 508000000,
  "views": 133786496664,
  "uploads": 993,
  "grade": "A++",
  "ranks": {
    "socialBlade": 1,
    "audience": 1,
    "views": 6,
    "country": 1,
    "category": 1
  },
  "linkedSocials": [
    { "url": "https://instagram.com/mrbeast", "title": "Follow" }
  ],
  "historyIncluded": true,
  "history": [
    {
      "date": "2026-07-05T00:00:00.000Z",
      "subscribers": 506000000,
      "views": 132387923880,
      "videos": 991
    }
  ],
  "fetchRoute": "proxy",
  "scrapedAt": "2026-07-19T00:00:00+00:00"
}

Counts change over time; this example demonstrates the output shape, not guaranteed current values.

How much does it cost to scrape SocialBlade creator stats?

The Actor uses pay-per-event pricing:

• a small one-time run-start charge;
• one creator-profile event for each successfully extracted profile;
• no profile charge for validation or fetch error records.

The formula-derived BRONZE profile price is $0.00442 per successful profile, or about $4.42 per 1,000 profiles, before ordinary platform usage. Higher Apify plans receive tiered discounts; the canonical curve is sized so even the DIAMOND tier covers measured compute and residential fallback cost at sustained volume.

Check the live Pricing tab before a production run because platform pricing is authoritative.

Residential proxy fallback may contribute ordinary platform proxy usage billed by Apify.

Scheduling creator watchlists

A scheduled watchlist turns snapshots into monitoring data.

Recommended workflow:

1. save a fixed profile list in an Apify Task;
2. run it daily or weekly with an Apify Schedule;
3. export each run to a warehouse or spreadsheet;
4. calculate change from previous snapshots;
5. alert when audience or rank movement crosses a threshold.

The source normally exposes about 15 daily history rows, but availability varies by creator.

Growth and ranking analysis tips

• Compare snapshots captured at the same time of day.
• Keep profileId as the durable join key.
• Treat ranks as directional signals, not absolute performance scores.
• Separate platform-specific comparisons when audience semantics differ.
• Preserve scrapedAt for reproducibility.
• Inspect historyIncluded before calculating history-based growth.
• Do not treat missing optional history as a failed profile.

Error handling and data quality

Invalid inputs produce uncharged error records with status: "error".

The run fails when every supplied target fails extraction. This prevents automation pipelines from silently accepting an empty success.

Common error causes include:

• unsupported SocialBlade routes;
• deleted or unavailable creators;
• temporary Cloudflare changes;
• a changed embedded application-state shape;
• disabled or misconfigured proxy access.

Successful rows and error rows can coexist in a watchlist run.

Proxy and concurrency guidance

SocialBlade frequently blocks direct and datacenter traffic.

The default configuration tries a direct request and then uses an Apify residential US proxy fallback.

Keep concurrency at 1–2 for ordinary watchlists. The maximum is intentionally limited to 5.

If a custom proxy is used, choose a stable geography and avoid rotating a creator through many retries.

Export and integrations

Apify datasets support JSON, CSV, Excel, XML, and RSS exports.

Useful integration patterns include:

• Google Sheets for campaign shortlists;
• Slack alerts for rank changes;
• Make or Zapier for no-code enrichment;
• BigQuery or Snowflake for historical analysis;
• webhooks for run-completion processing;
• Python or Node.js for custom scoring;
• Apify Schedules for recurring watchlists.

Use with the Apify API: cURL

curl -X POST \
  "https://api.apify.com/v2/acts/automation-lab~socialblade-creator-stats-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "profiles": [{"platform":"youtube","username":"mrbeast"}],
    "includeHistory": true,
    "maxProfiles": 1
  }'

Poll the returned run ID, then read the run's default dataset.

Use with the Apify API: JavaScript

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const input = {
  profiles: [{ platform: 'youtube', username: 'mrbeast' }],
  includeHistory: true,
  maxProfiles: 1,
};

const run = await client.actor(
  'automation-lab/socialblade-creator-stats-scraper'
).call(input);

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Keep API tokens in environment variables or a secret manager.

Use with the Apify API: Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ["APIFY_TOKEN"])
run = client.actor(
    "automation-lab/socialblade-creator-stats-scraper"
).call(run_input={
    "profiles": [{"platform": "youtube", "username": "mrbeast"}],
    "includeHistory": True,
    "maxProfiles": 1,
})

items = client.dataset(run["defaultDatasetId"]).list_items().items
print(items)

The same dataset view is available through the Console and API.

Use with MCP and AI assistants

Connect Apify's MCP server to Claude Code or another compatible client.

Claude Code

claude mcp add --transport http apify \
  "https://mcp.apify.com?tools=automation-lab/socialblade-creator-stats-scraper"

Claude Desktop

Add this server to your Claude Desktop configuration:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=automation-lab/socialblade-creator-stats-scraper"
    }
  }
}

Cursor

Open Cursor Settings → MCP, add a remote HTTP server, and use the same https://mcp.apify.com?tools=automation-lab/socialblade-creator-stats-scraper URL.

VS Code

Open the MCP server configuration in VS Code, add an HTTP server named apify, and use the same actor-scoped MCP URL.

Example prompts:

• “Get the latest SocialBlade stats and ranks for these five creators.”
• “Compare available 15-day audience growth across this YouTube watchlist.”
• “Return creators with an A or better SocialBlade grade.”
• “Export the results as a table grouped by country.”

Responsible and legal use

The Actor extracts publicly available creator-profile data.

You are responsible for complying with applicable laws, platform terms, and contractual obligations.

Do not use the output for harassment, discrimination, invasive profiling, or decisions that require consent or protected personal data.

Use reasonable schedules and avoid unnecessary repeated requests.

SocialBlade and the supported social platforms are trademarks of their respective owners. This Actor is not affiliated with or endorsed by them.

Limitations

• SocialBlade may change its page or embedded state without notice.
• Optional history can be absent for an otherwise valid profile.
• Not every metric exists on every platform.
• Private, deleted, disabled, or unsupported profiles may return errors.
• This Actor does not access paid SocialBlade dashboards or private APIs.
• It does not estimate sponsorship value or earnings.
• It does not search SocialBlade rankings or discover creators in v1.
• Platform counts may be rounded or delayed by the source.

Troubleshooting

Why did I receive an error record?

Check that the URL is a creator profile on socialblade.com and that its platform is supported. Open the URL manually to confirm the creator exists.

Why did the run fail instead of returning an empty dataset?

All targets failed. The Actor deliberately exits non-zero on total extraction failure so scheduled pipelines can alert rather than silently continue.

Why is history empty?

The creator profile was useful, but SocialBlade did not expose history for that target. Check historyIncluded and preserve the current snapshot.

Why is the proxy route shown?

Direct traffic was blocked and the residential fallback delivered the public profile state.

FAQ

Can I mix platforms in one run?

Yes. URL and structured inputs can include all five supported platforms.

Are duplicate profiles charged twice?

No. Targets resolving to the same canonical SocialBlade URL are deduplicated before extraction.

Are failed records charged as creator profiles?

No. The profile event is emitted only after useful profile data is parsed.

Can I disable history?

Yes. Set includeHistory to false for smaller output records.

Can I disable the direct attempt?

Yes. Set directFirst to false when you want to go directly to the configured proxy.

Does it require a SocialBlade login?

No. The Actor uses public creator profile pages only.

Related scrapers

Combine creator snapshots with other Automation Lab actors when a workflow needs source-specific content:

• YouTube Channel Search Scraper for creator discovery;
• YouTube Channel Scraper for platform-native channel metrics;
• Instagram Scraper for platform-native profile and content enrichment;
• Twitch Channel Stream Schedule Scraper for stream planning data.

Choose related actors only when their current Store scope matches your workflow.

Support

For reproducible support requests, include:

• the Actor run ID;
• a redacted example input;
• the affected SocialBlade URL;
• whether the issue affects every target or one creator;
• the error record and relevant log message.

Do not include your Apify token in support messages.