Creator data: what the official APIs give you, and what they do not

To scrape creator data, start with the official platform APIs, which give content and identity data but withhold audience demographics, reach and history. Ask creators directly for the withheld fields. Scrape public pages only for what remains, and treat the result as personal data. Several popular metrics, such as follower count, also mislead even when collected correctly.

Key takeaways

• Use the official API first: it covers content and identity, but platforms keep audience demographics and reach for advertisers and creators.
• Ask creators for their own platform screens or media kit to get the fields platforms withhold.
• Store timestamped raw counts on every collection, because a historical series cannot be collected retrospectively.
• Treat follower count as a filter, and rank on the median of recent engagement.
• Creator profiles are personal data, so set a lawful basis and a retention period even when the data is public.

What we'll cover

• What the official APIs actually give you
• The data platforms will not hand over
• Where scraping sits
• The numbers that mislead
• Building it with CodeWords
• Asking the creator, which is underrated
• Personal data, which most of this is
• Designing for a source that will break
• What to collect, and what to compute
• Making it survive
• Limits worth knowing about
• What to build first
• Frequently asked questions

What the official APIs actually give you

Official platform APIs give content and identity data readily and audience data sparingly. Check each platform's current API documentation for exact fields and access tiers before you build, because both change.

YouTube's Data API is among the most open, covering channel statistics, video metadata, search and playlists. If your work is YouTube-heavy, most of what you need is available through the official route.

Other platforms return content and identity, and follower counts are often available. The composition of that following is rarely available.

Access tiers change. Some platforms have moved to paid API access, so budget for it and check the free tier's limits before you plan research on it.

The rule of thumb: a platform keeps back anything it sells as an advertising or partnership product. That boundary explains most of what is and is not available.

The data platforms will not hand over

Platforms do not hand over five kinds of data, and these are the fields people most often set out to scrape.

Audience demographics. Age, location and gender splits are available to the creator and to advertisers, not to observers.

Reach and impressions. What a post was shown to, as distinct from what it received.

Historical series. Most APIs give a current value, not a trend. To get a trend, collect it yourself over time, which means starting now.

Deleted or edited history. Gone, and reconstructing it is its own problem.

Anything about the audience as people. Platforms withhold this deliberately.

For the first two, the honest routes are asking the creator or using the platform's own partnership tools. No technical shortcut exists.

Where scraping sits

Scraping creator data sits between permitted and actionable, depending on what you take and from where. Check the platform's terms and take legal advice for your jurisdiction before you scrape.

Platform terms commonly restrict automated collection. Breaching them is a contractual matter, and the usual consequence is blocking or account termination.

Law varies by jurisdiction and by what you take. Publicly visible information, accessed without circumventing a technical restriction, sits differently from anything behind a login or an anti-bot measure.

Data protection applies regardless. Creator profiles are personal data in most jurisdictions, and public availability does not remove the obligations that attach to collecting and storing them.

The sensible order is: official API first, then the platform's own partnership tooling, then asking the creator, and only then scraping public pages for the remainder. Where you scrape, take the minimum, identify yourself honestly, respect rate limits, and circumvent nothing.

The numbers that mislead

Five common creator metrics mislead even when collected correctly.

Follower count is the weakest signal available and the easiest to inflate. Ranking on it produces a list ordered by who bought the most followers.

Engagement rate depends on its denominator. Engagements over followers and engagements over reach give very different answers. Reach is the meaningful denominator, and observers cannot see it.

Averages hide the distribution. One viral post lifts an average while saying little about typical performance. Use the median.

Recency matters more than volume. A creator whose last six months are flat looks fine on lifetime totals.

Cross-platform comparison is mostly invalid, since a like means something different on each platform.

In practice: compute the median instead of the mean, weight recent activity, and use follower count as a filter, not a ranking.

Building it with CodeWords

CodeWords connects to 3,000+ integrations (CodeWords pricing page, 2026), and each connection is made once and reused.

1. Open CodeWords and start a new automation.
2. Describe what should happen in plain language to Cody, the automation builder: which creators to track, which fields matter, and how often to refresh.
3. Authorize the connections to the platform APIs you have access to and to wherever the data should land.
4. Describe the exceptions: a source that returns nothing, a rate limit, a creator whose account has gone.
5. Store a timestamped snapshot on every collection instead of overwriting, since the series is the part you cannot get retrospectively.

You describe the outcome; Cody builds it, connects it and deploys it. The free plan covers light use, with Pro at $39 per month and Business at $100 per month as usage grows (CodeWords pricing page, 2026). Details are on the pricing page.

Asking the creator, which is underrated

Asking the creator is the route that works for the fields that matter most. Creators can see their own demographics, reach and historical performance, and a serious enquiry usually gets a screenshot or an export. Many already have a media kit.

Asking has three advantages beyond availability. The data comes from the platform, not from your estimate. How the creator responds tells you something, since a clear export signals a different proposition from none. And you have made contact, which was the point of the research.

Self-reported figures can be selective, so ask for the platform's own screens instead of a summary. Use collected data to shortlist and the direct request to verify.

Personal data, which most of this is

A database of creator profiles is a database of personal data, however public each item was. Public availability is not consent and does not exempt you from the obligations.

Those obligations are four: hold a lawful basis, be able to say what you hold and why, apply a retention period, and respond when somebody asks what you hold about them.

Two practical steps follow. Collect the fields you will use instead of everything available, because every extra field is more to justify and delete. And keep the data somewhere you can query and purge, not scattered across exports.

Designing for a source that will break

Design every source to break, because scraped sources change without notice and platform access tiers change too.

Isolate each source behind its own component, so one failure does not stop the rest.

Validate what comes back. A follower count of zero is more likely a broken parse than a real value, and a pipeline that stores it quietly corrupts the dataset.

Alert on shape changes, not just errors. Silent success that returns nothing useful can go unnoticed for weeks.

Keep raw responses for a while, so a parsing bug can be corrected without recollecting.

Make sources swappable, not woven throughout the pipeline.

What to collect, and what to compute

Collect primitives and compute everything derived, because derived values change definition and primitives do not.

Store per observation: the timestamp, the identity, the follower or subscriber count, the post identifiers with their own timestamps, and the raw engagement counts. That is enough to compute anything later.

Compute and do not store: engagement rates, medians, growth rates, posting cadence and any score you invent. When the formula changes, recomputing from primitives takes an afternoon, while recollecting past data is impossible.

Making it survive

Five practices keep the dataset trustworthy.

Use the official API first, every time.

Snapshot with timestamps, and never overwrite.

Store primitives and compute the rest.

Validate values before storing them.

Apply a retention period, since this is personal data.

Limits worth knowing about

Five limits apply to creator data.

Audience demographics and reach are unavailable to observers, by design.

Follower count is the weakest signal and the easiest to inflate.

Platform terms commonly restrict automated collection, and blocking is the usual consequence.

Public availability does not remove data protection obligations.

Historical series cannot be obtained retrospectively, which is the case for starting collection before you need it.

What to build first

Build a timestamped snapshot of the primitives for a small set of creators, from official APIs only, on a schedule. Skip the score, the dashboard and the scraper for now. The series is what you cannot get later, and every week of delay is a week missing from it.

Two habits make the difference. Store raw counts and compute every derived figure, since you will change your definition of engagement rate. And ask creators directly for the fields platforms withhold, because a message gets better data than inference and starts the conversation you wanted anyway.

Frequently asked questions

Which platform APIs give the most creator data?

YouTube's Data API is among the most open, with channel statistics, video metadata, search and playlists. Most other platforms provide content and identity data readily and audience data sparsely or not at all. Check each platform's current documentation before building.

Why can I not get audience demographics?

Platforms keep audience demographics for creators and advertisers because they sell that data as an advertising and partnership product. Observers do not get it through public APIs. The honest routes are asking the creator or using the platform's partnership tools.

Is scraping creator data legal?

It depends on what you take and from where. Platform terms commonly restrict automated collection, and the legal position worsens where you circumvent a technical restriction or access anything behind a login. Data protection applies regardless, so take legal advice for your jurisdiction.

Does public data avoid data protection obligations?

No. A creator profile is personal data, and public availability is not consent. You still need a lawful basis, a retention period, and the ability to answer a request about what you hold on a person.

Why is follower count a poor metric?

Follower count is the easiest number to inflate and the least connected to outcomes. Ranking on it produces a list ordered by who bought the most followers. Use it as a filter, and rank on median recent engagement instead.

What is wrong with engagement rate?

The denominator decides the answer. Engagements over followers and engagements over reach differ greatly, and reach is the meaningful one. Observers cannot see reach, so ask creators for it from their own platform screens.

Should I use the mean or the median?

Use the median, weighted towards recent activity. One viral post distorts an average substantially while saying little about typical performance. The median shows what a typical post achieves, and recent posts show current form.

How do I get the data platforms withhold?

Ask the creator. Creators can see their own demographics and reach, and most have a media kit. Request the platform's own screens instead of a summary, and note how clearly they respond, since that tells you something useful.

What should I store?

Store timestamped primitives: identity, follower count, post identifiers and raw engagement counts. Compute rates, medians and scores from those. Definitions change over time, while the raw counts do not, so recomputing stays possible.

How do I handle a source that breaks?

Isolate each source, validate returned values before storing them, alert on shape changes as well as errors, and keep raw responses. A parsing bug can then be fixed retrospectively without recollecting the data.

Related reading

• Where AI actually helps a channel
• Scraping prices, and why it is adversarial
• Which Google credential you need