Google Analytics Hub API
Browse all Google APIs42
AI ReadinessFoundational (D-)42/100
Official vendor OpenAPI document · agent-readyAnalyticsData Pipelinesoauth216 EndpointsREST
For Agents
Publish, subscribe to, and manage shared BigQuery data products via Analytics Hub data exchanges, listings, and subscriptions.
Use for: List all Analytics Hub data exchanges I can publish into, Create a new listing under an existing data exchange, Subscribe my project to a published listing, Refresh an existing Analytics Hub subscription
Not supported: Does not run BigQuery queries, copy datasets, or manage compute reservations - use for Analytics Hub data exchanges, listings, and subscriptions only.
Analytics Hub is Google Cloud's data exchange built on top of BigQuery. The API manages data exchanges, listings (the published shareable assets), and subscriptions (the consumer side that surfaces a listing in a destination project's BigQuery dataset). It supports listing, creating, subscribing, refreshing, and revoking these resources, plus IAM-style policy management on each. It is intended for organisations that publish or consume data products across project, team, or organisation boundaries.
Install Jentic One Beta
Connect the Analytics Hub API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Analytics Hub 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fanalyticshub" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fanalyticshub" | 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 Analytics Hub API.
List data exchanges available within an organisation or under a project parent
Create a new listing in an exchange that publishes a BigQuery dataset for sharing
Subscribe a destination project to a published listing so it appears as a linked dataset
Refresh a subscription to pull the latest version of a published dataset
Revoke a subscription to stop a consumer from accessing a shared listing
Read and update the IAM policy on an exchange or listing for fine-grained access control
List subscriptions on a listing to audit which consumer projects have access
Use Cases
Patterns agents use Analytics Hub API for, with concrete tasks.
★ Cross-Team Data Product Publishing
A central data platform team curates BigQuery datasets and wants other teams across the organisation to subscribe to them rather than duplicating or copying tables. The Analytics Hub API creates a data exchange, registers a listing pointing at the source dataset, and exposes the listing for consumers to subscribe to. The consumer's BigQuery sees a linked dataset with no copy or storage cost.
POST /v1/{+parent}/dataExchanges to create the exchange, then POST /v1/{+parent}/listings with a bigqueryDataset source pointing at projects/{p}/datasets/{ds}.
Consumer Subscription Workflow
A consumer team wants to subscribe to a published listing so the dataset appears in their own BigQuery project. Calling :subscribe on the listing creates a linked dataset in the destination project. :refresh keeps the subscription current after the publisher updates the source, and :revoke ends access. This replaces ad-hoc table copies and email requests for access.
POST /v1/{+name}:subscribe on the listing with destinationDataset set to the consumer's project, then schedule periodic POST /v1/{+name}:refresh on the resulting subscription.
Access Audit on Shared Listings
Compliance teams need to know which consumer projects subscribe to a sensitive listing and revoke any that should no longer have access. List subscriptions on the listing returns each consumer subscription, and per-subscription IAM gives the binding details. A periodic audit job iterates these and emits a report.
List subscriptions under the listing, GET /v1/{+name} for each to capture state and consumer project, and surface anything that no longer matches the access policy.
Agent-Led Data Sharing
An agent integrating Analytics Hub through Jentic can interpret 'share this dataset with the analytics team' as a chain of create-listing and subscribe operations. Jentic isolates the Google Cloud service account and exposes the operation schemas, so the agent does not need bespoke OAuth or BigQuery dataset wiring code - the data exchange, listing, and subscription steps are direct tool calls.
Use the Jentic search query 'create an Analytics Hub listing' to discover /v1/{+parent}/listings, create the listing, then call :subscribe to attach the consumer project.
Key Endpoints
16 endpoints — analytics hub is google cloud's data exchange built on top of bigquery.
METHOD
PATH
DESCRIPTION
GET
/v1/{+organization}/dataExchanges
List data exchanges visible to an organisation
GET
/v1/{+parent}/dataExchanges
List data exchanges under a project parent
GET
/v1/{+parent}/listings
List listings under a data exchange
GET
/v1/{+parent}/subscriptions
List subscriptions under a parent
POST
/v1/{+name}:subscribe
Subscribe a consumer project to a listing
POST
/v1/{+name}:refresh
Refresh an existing subscription
POST
/v1/{+name}:revoke
Revoke a subscription
GET
/v1/{+organization}/dataExchanges
List data exchanges visible to an organisation
GET
/v1/{+parent}/dataExchanges
List data exchanges under a project parent
GET
/v1/{+parent}/listings
List listings under a data exchange
GET
/v1/{+parent}/subscriptions
List subscriptions under a parent
POST
/v1/{+name}:subscribe
Subscribe a consumer project to a listing
POST
/v1/{+name}:refresh
Refresh an existing subscription
POST
/v1/{+name}:revoke
Revoke a subscription
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
A
Analytics Hub API
- Foundational (D-)42/100
58
Foundational Compliance56
Developer Experience & Jentic Compatibility20
AI-Readiness & Agent Experience94
Agent Usability63
Security56
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
58
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: C+Signals: 4
70%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
60%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
20
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
79%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
63
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
62%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
56
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: CSignals: 1
56%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Analytics Hub API by hand means configuring Google OAuth 2.0 from a service account, rotating short-lived access tokens yourself, and pointing calls at the analyticshub.googleapis.com host. Through Jentic you install once, import the Analytics Hub API from the API Directory, store the OAuth credential once, and your agent calls it.
Permission scoping
Analytics Hub puts the parent and resource names in the URL path (/v1/{+parent}/dataExchanges, /v1/{+name}:subscribe), so a rule can pin your agent to one project's exchanges and listings: it can read them and nothing else. You choose the operations it may call, so actions like subscribe, refresh, or revoke are not included unless you add them.
Credential isolation
Your Google service account credential is stored once, encrypted, by your own Jentic One instance and rotated into short-lived access tokens at execution time. The key never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create an Analytics Hub listing' or 'subscribe to a data exchange', and Jentic returns the matching Analytics Hub operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Analytics Hub API through Jentic.
What authentication does the Analytics Hub API use?
OAuth 2.0 with the cloud-platform or bigquery scopes, typically via a Google Cloud service account that holds Analytics Hub roles on the relevant resources. Jentic stores the service account JSON in your Jentic One instance and only short-lived access tokens reach the agent.
Can I subscribe a consumer project to a listing through the API?
Yes. Call POST /v1/{+name}:subscribe on the listing with the consumer's destinationDataset, and a linked BigQuery dataset is created in that consumer project. Use :refresh to update and :revoke to remove access.
What are the rate limits for the Analytics Hub API?
Analytics Hub is governed by per-project Google Cloud quotas listed under the Analytics Hub service. Subscriptions are also subject to BigQuery dataset and project limits in the destination project.
How do I publish a BigQuery dataset as a listing through Jentic?
Search Jentic for 'create an Analytics Hub listing', load the schema for /v1/{+parent}/listings, and execute it with a bigqueryDataset source pointing at projects/{p}/datasets/{ds}. Run pip install jentic and use the async search, load, execute pattern.
Does Analytics Hub copy the source dataset?
No. Listings are linked datasets - consumers query the publisher's data in place via BigQuery. The publisher pays storage and the consumer pays query compute, so there is no duplicate storage cost from sharing through Analytics Hub.
Can I limit what my agent is allowed to do with the Analytics Hub API?
Yes. Because you run Jentic One yourself, your own rules decide which Analytics Hub operations and credentials the agent may use. Since the API puts the parent and resource names in the URL path (such as /v1/{+parent}/dataExchanges and /v1/{+name}:subscribe), you can pin the agent to one project's exchanges and listings so it only reads them. You also choose the exact operations it can call, so write actions like subscribe, refresh, or revoke are excluded unless you add them.
GET STARTED