Social Blade Multi-Platform Analytics Scraper accepts one required field and several optional controls.
| Field | Type | Required | Default / limits | Description |
|---|---|---|---|---|
profiles |
Array of strings | Yes | 1–1,000 items | Social Blade profile URLs or bare handles. |
defaultPlatform |
String enum | No | youtube; youtube, tiktok, twitch, instagram, facebook |
Platform used when a submitted value is a bare handle. |
includeDailyHistory |
Boolean | No | true |
Include available daily metric rows. |
historyDays |
Integer | No | 31; 1–31 |
Maximum requested daily history window per profile. |
includeWeeklyHistory |
Boolean | No | true |
Include available weekly summary rows. |
includeMonthlyHistory |
Boolean | No | true |
Include available monthly metric rows. |
includeGrowthMetrics |
Boolean | No | true |
Request growth metrics when supported. |
includeEarningsEstimates |
Boolean | No | true |
Request public earnings estimates when exposed. |
maxProfiles |
Integer | No | 0; 0–1,000 |
Maximum submitted profiles to attempt; 0 means all inputs. |
Complete Social Blade URLs may be mixed with bare handles:
{
"profiles": [
"https://socialblade.com/youtube/handle/mrbeast",
"https://socialblade.com/instagram/user/instagram",
"ninja"
],
"defaultPlatform": "twitch"
}Complete URLs are normalized to the canonical Social Blade platform route. A bare handle uses defaultPlatform, which defaults to YouTube. Only HTTPS Social Blade profile routes are accepted as URLs.
The smallest valid request is:
{
"profiles": [
"https://socialblade.com/youtube/handle/mrbeast"
]
}Apify applies the schema defaults when optional fields are omitted. The Actor also keeps the same safe fallbacks for compatible direct execution. Setting all history switches to false requests current profile data without time-series rows. historyDays only limits daily history; weekly and monthly availability depends on the public source.
No proxy configuration or source credentials are accepted as Actor input.
Invalid values receive an auditable error record without an upstream request. Equivalent profiles are fetched once; later duplicates are recorded without a second fetch or profile charge. A valid profile can still be partial when an attempted endpoint fails. Platform coverage differences are reported in dataQuality rather than inferred values.