Google YouTube Reporting API
Browse all Google APIs✓ Official Vendor SpecAnalyticsData Pipelinesoauth28 EndpointsREST
For Agents
Schedule recurring bulk CSV exports of YouTube channel analytics and download the resulting report files. For warehousing and historical backfill rather than live queries.
Use for: List available YouTube reporting types, Create a daily channel performance reporting job, List all reports produced by a specific job, Download a daily report CSV by resourceName
Not supported: Does not handle real-time parameterised queries, video uploads, comment moderation, or non-YouTube data exports — use for scheduled bulk CSV exports of YouTube analytics only.
The YouTube Reporting API schedules and downloads bulk CSV reports of YouTube channel and content analytics. Clients pick a reportType, create a recurring job, and pull the daily report files generated against the authorised channel. This is the right API for warehousing, backfilling, and large-scale analytics work where parameterised live queries are impractical; YouTube Analytics handles the ad-hoc, real-time use case.
Install Jentic One Beta
Connect the YouTube Reporting API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the YouTube Reporting 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 Reporting API.
List available reportTypes covering channel, content owner, and ad performance
Create a recurring reporting job for a chosen reportType
List existing jobs and pull the reports they have produced
Download a specific report CSV by its resourceName
Delete a reporting job that is no longer needed
Use Cases
Patterns agents use YouTube Reporting API for, with concrete tasks.
★ Warehouse load of channel analytics
Data teams pull historical channel and video analytics into BigQuery or another warehouse by creating reporting jobs for the relevant reportTypes and downloading the daily CSVs. Because reports are pre-computed by YouTube, they are far cheaper to consume than running parameterised analytics queries every hour. Backfills run by enumerating /v1/jobs/{jobId}/reports across past days.
Create a job for reportType channel_basic_a2 via POST /v1/jobs, then list /v1/jobs/{jobId}/reports for a date range and download each via /v1/media/{resourceName}.
Multi-channel network reporting
Networks managing many channels prefer the Reporting API for its content-owner reportTypes that aggregate across an entire network in a single CSV. This avoids running thousands of per-channel analytics queries and produces a clean partitioned dataset suitable for downstream BI work. The reportTypes endpoint advertises which content-owner reports the authorised account can subscribe to.
List available reportTypes, find ones starting with content_owner_, create jobs for the relevant types, and store the resulting CSVs partitioned by date.
Ad performance backfill
Teams analysing monetisation pull ad-performance reportTypes — covering ad impressions, monetised playbacks, and partner revenue — into the warehouse alongside content metrics. This produces a unified dataset for forecasting and creator payout reconciliation. Because the API is bulk and idempotent, late-arriving corrections from YouTube can be re-pulled without complex deduplication logic.
Create a reporting job for an ad-performance reportType, then daily download the latest report and load it into a warehouse table partitioned by date.
Agent-driven backfill orchestration through Jentic
A data-platform agent can manage YouTube reporting jobs — creating, pausing, and re-pulling reports during a backfill — through Jentic without engineers writing job-management code. The agent searches Jentic for create youtube reporting job, loads the operation schema, and executes against each reportType. Tokens stay isolated in the Jentic vault.
Through Jentic, list reportTypes, create a job for each one the team needs, and emit a list of jobIds and the first reports each one produced.
Key Endpoints
8 endpoints — the youtube reporting api schedules and downloads bulk csv reports of youtube channel and content analytics.
METHOD
PATH
DESCRIPTION
GET
/v1/reportTypes
List available report types
POST
/v1/jobs
Create a reporting job
GET
/v1/jobs
List existing jobs
GET
/v1/jobs/{jobId}/reports
List reports for a job
GET
/v1/jobs/{jobId}/reports/{reportId}
Get report metadata
GET
/v1/media/{+resourceName}
Download a report CSV
GET
/v1/reportTypes
List available report types
POST
/v1/jobs
Create a reporting job
GET
/v1/jobs
List existing jobs
GET
/v1/jobs/{jobId}/reports
List reports for a job
GET
/v1/jobs/{jobId}/reports/{reportId}
Get report metadata
GET
/v1/media/{+resourceName}
Download a report CSV
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
OAuth 2.0 client credentials and the authorising user's refresh token are stored encrypted in the Jentic vault. Agents receive scoped access tokens at execution; raw refresh tokens never leave the vault.
Intent-based discovery
Agents call Jentic search with intents like create a youtube reporting job or list available report types and Jentic returns the matching operation with its input schema.
Time to first call
Direct integration: 1-2 days for OAuth, job creation, and CSV download pipeline. Through Jentic: under an hour to schedule the first job and pull a report.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using YouTube Reporting API through Jentic.
What authentication does the YouTube Reporting API use?
OAuth 2.0 (Oauth2 and Oauth2c schemes) with the youtube.readonly or yt-analytics.readonly scope for channel reports, and yt-analytics-monetary.readonly for monetary data. Through Jentic the OAuth credentials are stored encrypted and short-lived access tokens are minted at execution time.
How is this different from the YouTube Analytics API?
Reporting produces scheduled bulk CSVs that you download and load into a warehouse. Analytics returns parameterised JSON results in real time. Reporting is cheaper and easier for backfills; Analytics is better for live dashboards. Most data teams use both for different layers of their stack.
What are the rate limits for the YouTube Reporting API?
Per-project quotas are managed in the Cloud Console under APIs and Services and are sized for job creation and report download volume. Job creation limits are low because reports run server-side; download throughput is the more common bound and depends on report size.
How do I create a reporting job through Jentic?
Search Jentic for create youtube reporting job, load the schema for POST /v1/jobs, and execute it with reportTypeId set to the desired type from /v1/reportTypes. The response includes the jobId; subsequent reports show up under /v1/jobs/{jobId}/reports daily.
How do I download a report file?
Each report has a resourceName. Call GET /v1/media/{+resourceName} to stream the CSV. The endpoint returns the raw report bytes; clients should write directly to disk or to a warehouse staging bucket rather than buffering in memory for large reports.
GET STARTED