YouTube Made for Kids API integrations must check status.madeForKids before embedding, uploading, or enabling tracking. This guide explains the MFK rules, quota impact, and safe branching logic.
YouTube ‘Made for Kids’: What Breaks in Your API Integration When a Video Is Flagged MFK
Two videos, same channel, same upload flow — and your integration treats them identically. One is designated ‘Made for Kids’. The other is not. YouTube’s API will tell you which is which, but only if your client is built to ask. Most embed tools, dashboards, and multi-tenant uploaders never do.
‘Made for Kids’ (MFK) is a formal per-video and per-channel designation on YouTube, driven by COPPA compliance — not a content-tone label you can infer from a title or thumbnail. For a normal viewer, YouTube just quietly turns features off. For an API client that embeds, manages, or uploads YouTube video on someone else’s behalf, MFK status changes what your integration is legally allowed to do with that video — and the API only tells you if you check.
YouTube Made for Kids API: the property most integrations never call
Google’s official YouTube Data API guide is explicit: to find out whether a video is MFK, you call the videos.list endpoint with the video ID and request, at minimum, the id and status parts. The result comes back in one field — status.madeForKids. There is no separate warning, no error state, no banner. If your client never requests the status part, or never reads that one field, it has no way of knowing.
Embedding MFK content
Google’s Developer Policies (§III.E.4.j) require that if you embed a video designated MFK, you must turn off tracking and make sure all data collection tied to that player is compliant with applicable laws, including COPPA. That obligation is per-video, not per-app — it only applies to the specific player instance showing MFK content.
Uploading MFK content
YouTube’s API Services Terms require an upload client to declare MFK status before or during upload, and Google’s Developer Policies scope programmatic uploading to a client’s own videos on its own channel — with a dedicated project ID prefix reserved for that Made-for-Kids upload path. It is a separate, narrower lane than general-purpose API access.
The quota cost of just checking
A new API project’s default allocation is 10,000 quota points per day. Google’s own MFK-status guide notes that’s enough to check the MFK status of up to roughly 5,000 videos — if that check is the only thing your project does that day. A dashboard or scheduler that manages content across dozens of client channels, and checks MFK status before every embed or every tracking decision, can spend a meaningful share of its daily quota purely on compliance lookups before it does anything else with the API.
What YouTube itself turns off on MFK content
Independently of any API integration, YouTube disables a set of standard viewer features on content designated MFK — including comments, live chat, the notification bell, Stories, save-to-playlist, and personalized advertising. An API client that mirrors YouTube’s own UI (comment widgets, playlist-save buttons, notification triggers) and doesn’t branch on MFK status will offer controls on an embed that YouTube itself has already switched off natively — a mismatch reviewers and users both notice.
Verify the workflow against Google's official YouTube Data API videos.list documentation before shipping.
YouTube Made for Kids API checks should run before every embed so tracking and personalization controls match the video status.
For a reliable YouTube Made for Kids API integration, request the status part and read status.madeForKids instead of guessing from titles.
A production-ready YouTube Made for Kids API client should branch cleanly when a creator changes the MFK designation later.
Document the YouTube Made for Kids API response in your audit notes so reviewers can see how the player disables data collection.
Separate upload handling from embed handling in the YouTube Made for Kids API project because quota and policy requirements differ.
Test the YouTube Made for Kids API path with flagged and unflagged videos before enabling multi-tenant publishing.
Pair this with the YouTube API compliance audit guide for a complete review.
Where multi-tenant products get caught out
- Treating ‘family-friendly’ branding as the same thing as an MFK designation — it isn’t; MFK is a formal status set by the uploader or YouTube, not a tone judgement
- Checking
status.madeForKidsonce and caching the result indefinitely, when a channel or video owner can change the designation later - Applying one tracking/personalization policy across every embedded video regardless of status
- Building an upload path that writes to a client’s channel without the dedicated Made-for-Kids project handling MFK uploads separately
- Assuming a quota-cost estimate for embeds or uploads without budgeting for the extra
videos.liststatus check per item
Why this is a setup problem, not a coding problem
None of this is solved by writing more error-handling. It is solved by the project structure being right from the start — the right scopes, the right project separation for Made-for-Kids uploads, and a compliance audit submission that shows Google your client actually branches on status.madeForKids instead of ignoring it. That is exactly the kind of setup and audit-preparation gap our YouTube API Approval Service is built to close, alongside the wider YouTube API compliance audit requirements and the upload-client UI rules Google checks before granting more quota.
status.madeForKidsis returned byvideos.listwhen thestatuspart is requested- Embedding MFK content requires disabling tracking for that player per §III.E.4.j of the Developer Policies
- A default 10,000-point daily quota covers roughly 5,000 MFK-status checks alone
- YouTube disables comments, live chat, notifications, and personalized ads on MFK videos independently of any API client
This article is general guidance based on YouTube’s published API Services Terms of Service and Developer Policies as of 2026, including the Finding the MadeForKids Status guide (last updated 2026-06-01). Platform policies change; always confirm current requirements in Google’s official documentation. We cannot promise a specific audit outcome, quota amount, or compliance determination.
Need Us to Get Your Google / YouTube API 100% Approved?
Stop losing weeks to OAuth verification back-and-forth and quota audits. With 500+ apps approved, we handle your entire submission from start to finish. You get 100% Approval or a 100% Refund — and for your complete safety, you can hire us directly through Upwork or Fiverr Escrow (or use the WhatsApp / Calendar buttons in the header & footer).
Chat on WhatsAppFrequently Asked Questions about YouTube API audit approval
Why do YouTube apps get flagged for made-for-kids handling?
Audits flag apps that don't let users set or respect the audience setting correctly, that collect or display data in ways that break the policies for kids' content, or that hide required settings in the upload flow.
How long does it take if you handle it?
It usually takes ~2–3 days for preparation and submission, followed by the platform's review queue — typically 7–15 days (often faster on platforms like X, or longer depending on platform review volume and any follow-up rounds).
What if it still isn't approved?
We work on a 100% Approval or 100% Refund basis: if we can't get your valid use case approved, you get a full refund.
Is it safe to hire you?
Yes. You can hire us through Upwork or Fiverr, so your payment stays in Escrow and is only released when the work is delivered. We've been doing this for 10+ years, with 500+ apps approved and 10,000+ permissions granted.