Google YouTube Analytics API
Browse all Google APIs✓ Official Vendor SpecAnalyticsProduct Analyticsoauth28 EndpointsREST
For Agents
Query YouTube channel and video analytics by metric, dimension, and filter. Manage analytics groups and items for cohort-based reporting. Read-only over OAuth.
Use for: Get views and watch time by day for the last 28 days, Retrieve top traffic sources for a specific video, List demographics for the channel's audience, Create a group of videos for cohort analytics
Not supported: Does not handle video uploads, comment moderation, monetisation configuration, or non-YouTube analytics — use for querying YouTube channel and video performance data only.
The YouTube Analytics API exposes channel and content performance data for the authorised YouTube account. It supports targeted reports — views, watch time, subscribers gained, demographics, traffic sources — driven by metric, dimension, and filter parameters, plus group and groupItem management to roll multiple videos or channels into named cohorts. This is the API for live, ad-hoc analytics queries; bulk historical exports use the separate YouTube Reporting API.
Install Jentic One Beta
Connect the YouTube Analytics API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the YouTube Analytics API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with YouTube Analytics API.
Run targeted reports combining metrics like views and estimatedMinutesWatched with dimensions such as day, country, or video
Filter reports by channel, video, group, or geographic region
Create analytics groups to bundle videos or channels for cohort analysis
Add and remove groupItems to maintain cohort membership over time
List existing groups and groupItems for the authorised account
Use Cases
Patterns agents use YouTube Analytics API for, with concrete tasks.
★ Creator dashboard with daily KPIs
Power a creator's internal dashboard with daily views, estimated watch time, and subscribers-gained pulled directly from YouTube Analytics. The reports endpoint accepts metric, dimension, and filter parameters so the dashboard can render channel-level overviews and per-video drill-downs from a single API surface. Refresh frequency is bounded by YouTube's analytics processing latency, typically 24-48 hours.
Call GET /v2/reports with ids=channel==MINE, metrics=views,estimatedMinutesWatched, dimensions=day, startDate and endDate covering the last 28 days, and return the rows.
Cohort analytics with groups
Studios and multi-channel networks group related videos — by show, season, or sponsorship — using the groups and groupItems endpoints, then run reports filtered by group ID. This produces clean cohort metrics without retrofitting tags on every video. The grouping API is the right primitive for any analytics workflow that needs stable cohort definitions over time.
POST /v2/groups to create a group named Q4 Sponsored, add three videos via POST /v2/groupItems, then GET /v2/reports filtered by group=={group_id}.
Audience demographic deep-dive
Marketing teams query demographic dimensions — ageGroup, gender, country — to understand who is watching specific videos before greenlighting follow-up content. The reports endpoint exposes these dimensions alongside engagement metrics in one query. This replaces the manual exports many teams used to copy out of YouTube Studio.
Call GET /v2/reports with metrics=viewerPercentage, dimensions=ageGroup,gender, and a filter on a specific video to get demographic breakdown.
Agent-driven channel reporting through Jentic
An analytics agent can compose multi-step reports — daily views, top videos, audience country mix — through Jentic without engineers writing OAuth and pagination glue. The agent searches Jentic for query youtube channel analytics, loads the reports operation, and executes it with the metrics and dimensions it needs. Tokens stay isolated inside the Jentic vault.
Through Jentic, run three GET /v2/reports calls covering daily views, top videos by watch time, and country breakdown, then summarise the result in plain English.
Key Endpoints
8 endpoints — the youtube analytics api exposes channel and content performance data for the authorised youtube account.
METHOD
PATH
DESCRIPTION
GET
/v2/reports
Run an analytics report
GET
/v2/groups
List analytics groups
POST
/v2/groups
Create an analytics group
GET
/v2/groupItems
List items in a group
POST
/v2/groupItems
Add an item to a group
DELETE
/v2/groupItems
Remove an item from a group
GET
/v2/reports
Run an analytics report
GET
/v2/groups
List analytics groups
POST
/v2/groups
Create an analytics group
GET
/v2/groupItems
List items in a group
POST
/v2/groupItems
Add an item to a group
DELETE
/v2/groupItems
Remove an item from a group
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
OAuth 2.0 client credentials and the channel owner's refresh token are stored encrypted in the Jentic vault. Agents receive scoped access tokens at execution; raw refresh tokens never enter the model context.
Intent-based discovery
Agents call Jentic search with intents like get youtube channel views or list audience demographics and Jentic returns the reports operation with metric and dimension parameters preconfigured.
Time to first call
Direct integration: 1-2 days for OAuth setup, scope verification, and pagination handling. Through Jentic: under an hour to run a first report.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using YouTube Analytics API through Jentic.
What authentication does the YouTube Analytics API use?
OAuth 2.0 (Oauth2 and Oauth2c schemes) with the youtube.readonly or yt-analytics.readonly scopes for read access. Reports are scoped to the authorised channel. Through Jentic the OAuth credentials are stored encrypted and short-lived access tokens are minted at execution time.
What is the difference between this API and YouTube Reporting?
YouTube Analytics is for ad-hoc, parameterised queries that return JSON in real time (with the standard analytics processing lag). YouTube Reporting is for scheduled bulk CSV exports of historical data and is better for warehousing. Many teams use both: Analytics for dashboards, Reporting for backfill.
What are the rate limits for the YouTube Analytics API?
Per-project quotas are managed in the Cloud Console under APIs and Services. The published default is in the order of tens of thousands of queries per day per project, which is enough for most dashboards. Heavy fan-out workloads should request a quota increase or batch queries by dimension.
How do I run a report through Jentic?
Search Jentic for query youtube analytics, load the schema for GET /v2/reports, and execute it with ids, metrics, dimensions, startDate, and endDate. Group filters and sort orders are exposed as additional query parameters.
Can I group videos or channels for cohort reporting?
Yes. POST /v2/groups creates a group, POST /v2/groupItems adds a video or channel, and DELETE /v2/groupItems removes one. Reports can then be filtered with group=={group_id} to scope metrics to that cohort.
GET STARTED