Product
Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing
Developers

GET STARTED

API DirectoryBrowse 10,000+ APIs Ready For AI Agent IntegrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI Readiness using our scorecardArazzo UIVisualize Arazzo Workflows As Interactive DocumentationArazzo EditorBuild And Edit Multi-Step API Workflows Visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
Resources
Company
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
Resources
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode

Install Jentic One Beta

Connect the Google Analytics API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Google 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fanalytics" | sh
2

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%2Fanalytics" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Google Analytics API.

Run Core Reporting queries against historical Universal Analytics data with dimensions and metrics

Run Multi-Channel Funnels (MCF) reports for attribution analysis on historical sessions

Manage UA accounts, web properties, and profiles (views) including their hierarchical relationships

Configure goals, filters, and unsampled report definitions on UA properties

GET STARTED

Start building with Google Analytics API

Explore with Jentic One
View OpenAPI Document

Manage entity user links to grant or revoke UA account, property, and view access

List and read realtime reports for any UA properties still receiving traffic during transition windows

Read account summaries to discover the full UA account, property, and view tree at once

Use Cases

Patterns agents use Google Analytics API for, with concrete tasks.

★ Historical Universal Analytics Reporting

Teams that ran Universal Analytics for years still need to query that history for year-over-year comparisons even after migrating to GA4. The Core Reporting endpoint /data/ga returns dimensions and metrics for a specified UA view ID and date range, and Multi-Channel Funnels at /data/mcf returns attribution paths. This is the only programmatic surface for UA historical data - GA4's Data API does not cover UA properties.

GET /data/ga with ids=ga:{viewId}, start-date and end-date, dimensions=ga:source,ga:medium and metrics=ga:sessions,ga:pageviews and write the rows to a warehouse table.

UA Property Inventory and Cleanup

Organisations migrating to GA4 need a clean inventory of every UA account, property, and view, and a way to revoke obsolete user access during sunset. /management/accountSummaries returns the full hierarchy in one call. The accounts, webproperties, profiles, and entityUserLinks paths support listing and (where allowed) updating these resources.

GET /management/accountSummaries and write the account, webPropertyId, and profileId tree to a CSV, then call entityUserLinks to list current users on each.

Goal and Filter Audit

Before retiring a Universal Analytics property, teams want to capture every goal and filter definition for institutional knowledge. The Management API exposes goals and filters per profile or account. A script can iterate accounts, properties, and views, capture the configured goals and filters, and store them as JSON for the GA4 migration team to translate.

List accounts, then iterate webProperties and profiles, calling /management/accounts/{accountId}/webproperties/{webPropertyId}/profiles/{profileId}/goals and the filters endpoint to capture every definition.

Agent Pull of Historical UA Reports

An agent integrating the Google Analytics v3 API through Jentic can run Core Reporting queries against historical UA data and answer questions about long-term trends. Jentic stores the OAuth credential and exposes the report request schema, so the agent does not have to write the OAuth dance or learn UA's metric and dimension naming by hand.

Use the Jentic search query 'run a Universal Analytics core reporting query' to discover /data/ga, then call it for a UA view ID with the requested dimensions, metrics, and date range.

Key Endpoints

88 endpoints — the google analytics api v3 (universal analytics) exposes both reporting and management for universal analytics properties - the predecessor to ga4.

METHOD

PATH

DESCRIPTION

GET

/data/ga

Run a Core Reporting query against a UA view

GET

/data/mcf

Run a Multi-Channel Funnels report

GET

/data/realtime

Run a real-time report

GET

/management/accountSummaries

List the UA account, property, and view hierarchy in one call

GET

/management/accounts

List UA accounts the caller can access

GET

/data/ga

Run a Core Reporting query against a UA view

GET

/data/mcf

Run a Multi-Channel Funnels report

GET

/data/realtime

Run a real-time report

GET

/management/accountSummaries

List the UA account, property, and view hierarchy in one call

GET

/management/accounts

List UA accounts the caller can access

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Google Analytics API by hand means setting up Google OAuth 2.0, minting short-lived access tokens from a refresh token, and pointing Universal Analytics calls at the analytics.googleapis.com host with the analytics.v3 path. Through Jentic you install once, import the Google Analytics API from the API Directory, store the OAuth credential once, and your agent calls it.

Permission scoping

The Universal Analytics surface carries the reporting query in the request body and management ids in the path, so limit the agent to the operations it needs, such as reading core reporting data or listing account summaries. You choose the operations it may call, so management writes are not included unless you add them.

Credential isolation

Your Google OAuth credential is stored once, encrypted, by your own Jentic One instance and exchanged for short-lived access tokens at execution time. The client secret and refresh token never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'run a Universal Analytics core reporting query' or 'list UA goals', and Jentic returns the matching Google Analytics 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.

Alternative

Google Analytics Data API

→

Data API queries GA4 property reports; UA v3 queries Universal Analytics historical data.

Use Data API for any GA4 reporting; use this API only for Universal Analytics historical data.

Alternative

Google Analytics Admin API

→

Admin API manages GA4 account and property configuration; UA v3 manages legacy Universal Analytics configuration.

Use Admin for GA4 property management; use this API for Universal Analytics property and view management.

FAQs

Specific to using Google Analytics API through Jentic.

What authentication does the Google Analytics v3 API use?

OAuth 2.0 with the analytics or analytics.readonly scopes. Jentic stores the OAuth refresh token in its encrypted vault and gives the agent only short-lived access tokens, so credentials never enter agent context.

Does this API let me query GA4 properties?

No. This is Universal Analytics (v3); GA4 properties are accessed via the Google Analytics Admin API (analyticsadmin) and the Google Analytics Data API (analyticsdata). Use this API only for historical UA data and UA property management.

What are the rate limits for the Google Analytics v3 API?

Universal Analytics enforces per-project, per-view, and per-second quotas on the Core Reporting and Management APIs. Default quotas are 50,000 requests per project per day for the Core Reporting API. Quotas are listed in IAM and Admin, Quotas under the Google Analytics API in the Cloud Console.

How do I run a Core Reporting query through Jentic?

Search Jentic for 'run a Universal Analytics core reporting query', load the schema for /data/ga, and execute it with ids=ga:{viewId}, start-date, end-date, dimensions, and metrics. Run pip install jentic and use the async search, load, execute pattern.

Is Universal Analytics still processing new data?

No. Standard Universal Analytics properties stopped processing new hits on 1 July 2023. This API now serves historical UA data and management of legacy property metadata; new analytics implementations should target GA4 via analyticsadmin and analyticsdata.

Can I limit what my agent is allowed to do with the Google Analytics API?

Yes. Because your Jentic One instance is self-hosted, your own rules decide which of the 88 Universal Analytics operations the agent may call, so you can allow it to read core reporting data at /data/ga or list account summaries at /management/accountSummaries while withholding everything else. Management writes such as updating accounts, goals, filters, or entityUserLinks are not included unless you add them. You also control which OAuth credential and scopes the agent may use, so a reporting agent can be restricted to read-only access.

APIs / Analytics / Google / Google Analytics API
Google Analytics API logo

Google Analytics API

Browse all Google APIs
39
AI ReadinessNon-Ready (F)39/100
See full scorecard
Official vendor OpenAPI document · agent-readyAnalyticsWeb Analyticsoauth288 EndpointsREST

For Agents

Read historical Universal Analytics report data and manage UA accounts, properties, views, goals, and filters across 88 endpoints.

Use for: Get the historical sessions and pageviews for a Universal Analytics view in 2022, Run a Core Reporting query for a specific UA view ID over a date range, List all Universal Analytics accounts I can access, Retrieve the goal definitions configured on a UA property

Not supported: Does not query GA4 properties, configure GA4 streams, or send measurement events - use for Universal Analytics reporting and management only.

The Google Analytics API v3 (Universal Analytics) exposes both reporting and management for Universal Analytics properties - the predecessor to GA4. It covers the Core Reporting API, Multi-Channel Funnels (MCF), Real Time, and the Management API for accounts, web properties, profiles (views), goals, filters, and user permissions. Universal Analytics stopped processing new data in 2023, so this API is now used primarily to read historical data and to manage legacy property metadata. New analytics work should target the GA4 Admin and Data APIs.

Jentic One on GithubView OpenAPI Document

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.

G

Google Analytics API

- Non-Ready (F)
39/100
50
Foundational Compliance
56
Developer Experience & Jentic Compatibility
18
AI-Readiness & Agent Experience
87
Agent Usability
63
Security
60
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
50

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: C-Signals: 4
87%

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).

14%

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.

18

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
72%

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.

87

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1
87%

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).

60

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: C+Signals: 1
60%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>