Skip to content

Latest commit

 

History

History
44 lines (34 loc) · 2.79 KB

File metadata and controls

44 lines (34 loc) · 2.79 KB

Output reference

The default Dataset contains one normalized profile record per unique valid input, followed by optional historical records when requested and available. Error and duplicate inputs remain auditable rather than disappearing.

Field Type Description
recordType String profile, dailyStat, weeklyStat or monthlyStat.
status String ok, partial or a stable error classification.
platform String Normalized platform name.
creatorId String or null Public source identifier when available.
username String or null Normalized public username or handle.
primaryAudience Integer or null Main subscriber, follower or audience count.
audience Object Platform audience counts such as subscribers, followers, views or likes.
content Object Video, upload, post, live-stream and unified media totals.
growth Object or null Public growth endpoint representation when available.
growthWindows Object or null Metric-first absolute deltas and percentages for supported windows.
rankings Object or null Current and maximum public rankings.
earnings Object or null Public earnings estimate when exposed.
earningsStatus String available, not_available or not_requested.
requestMetrics Object Collection timing, request counts and per-endpoint status.
dataQuality Object Available, failed, unavailable, missing and not-requested endpoints.
scrapedAt String UTC observation timestamp.

Status values

Status Meaning
ok A usable public profile snapshot was delivered.
partial The profile was valid but an endpoint that the Actor attempted failed.
invalid_input The submitted URL or handle was not supported.
duplicate An equivalent profile was already submitted in the run.
failed Collection did not succeed after the allowed retry.

Historical records

Daily, weekly and monthly records contain the profile identity, date and normalized metric values. Historical rows are emitted only when the public source returns usable dated data. They do not create separate billing events.

Platform coverage

Social Blade does not expose identical fields for every platform. For example, public Instagram coverage can provide a current profile snapshot and maximum ranks while some statistics or history endpoints are unavailable without login. The Actor reports those endpoints as unavailable and does not attempt login or bypass access controls.

Complete example

data/sample-output.json contains a sanitized profile item from a successful YouTube collection. data/sample-output.csv is a flattened export of the same profile record.