Loading...
Loading...
Product / API
Understand API capabilities and integration touchpoints in the broader product architecture.
Open Dashboard > Settings > API Keys to create, copy, or revoke keys on Pro and Enterprise plans.
Reference endpoints, payloads, authentication patterns, and monthly API allowances.
Machine-readable endpoint contract for tools, agents, and internal integrations.
Model Context Protocol manifest with discovery links and product contract metadata.
Human-readable guide to the MCP transport, resources, and tool surface.
Crawler and agent guidance for discovery, citation, and retrieval workflows.
Machine-readable plan, trial, and checkout details for agent crawlers.
Compact index that points agents at pricing, docs, and protocol surfaces.
Developer onboarding, webhooks, SDKs, and rate-limit guidance.
Current integrations and implementation guidance.
The TubeAnalytics public API exposes channel metrics, video performance data, and competitor benchmarks over a standard REST interface authenticated with API keys. Developers use it to pull YouTube analytics data into custom dashboards, BI tools, Google Sheets automations, or internal reporting pipelines — without building a direct YouTube API integration.
The API mirrors the same data available in the TubeAnalytics dashboard — RPM, CPM, views, watch time, subscriber changes, traffic sources, and audience demographics — in a machine-readable format with consistent pagination and predictable response schemas. All endpoints return JSON and support range parameters for historical queries.
API keys are issued at the organization level and passed via the Authorization header as a Bearer token. Keys can be created, rotated, and revoked from the developer settings panel without affecting connected YouTube channel credentials or other users in the workspace.
If you are on Pro or Enterprise, you can jump straight to Dashboard > Settings > API Keys to create and manage keys. The API keys tab is hidden for Starter accounts, and the UI will show an upgrade prompt instead.
API access currently ships with the Enterprise plan. Monthly API call allowances scale with the plan contract, and the public pricing surface now shows those usage limits alongside the subscription tiers. The API returns standard 429 responses with Retry-After headers when a limit is reached.
Agencies frequently use the API to feed channel performance data into client-facing Looker Studio or Tableau dashboards. By pulling data nightly or on-demand through the API, they maintain a single source of truth without manually exporting reports for each client account.
Product teams embed the API in internal tools that surface YouTube performance alongside other business metrics — pairing channel RPM trends with ad spend data or linking video release schedules with audience growth curves. The consistent API schema makes these joins straightforward regardless of the underlying BI platform.
The public discovery files live at /openapi.json, /mcp.json, /ai-pricing.json, /agents.txt, and /ai.txt. Those endpoints make the API surface easier to index for agents, validate against tooling, and reuse in documentation generators without scraping the human-facing pages.
Use developer documentation to implement quickly, or contact the team for advanced workflows.