Google Chrome Management API

Name: Chrome Management API
Brand: Google Chrome Management API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsMonitoring Observabilityoauth222 Endpoints

Install Jentic One Beta

Connect the Chrome Management API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Chrome Management 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.

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 | sh

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 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 Chrome Management API.

Count Chrome browsers and devices that need administrator attention

Aggregate Chrome version distribution across the managed fleet

List installed apps and extensions and the users requesting them

GET STARTED

Start building with Chrome Management API

Explore with Jentic

View OpenAPI Document

For Agents

Read managed-browser and ChromeOS device telemetry, app and extension inventories, crash events, and printing reports for a Google Workspace customer.

Use for: List installed Chrome extensions across our managed fleet, Find which devices are running an outdated Chrome version, Count Chrome crash events for the last 28 days, Identify users requesting a specific Chrome extension

Not supported: Does not apply Chrome policies, manage user accounts, or write device configuration - use for read-only Chrome and ChromeOS telemetry and inventory only.

Use Cases

Patterns agents use Chrome Management API for, with concrete tasks.

★ Extension Risk Inventory

Security teams enumerate every Chrome extension installed across the managed fleet, cross-reference against a risk feed, and act on high-risk extensions in policy. countInstalledApps and fetchUsersRequestingExtension provide the inventory and the user-level requests respectively, which feed into a periodic compliance report. Most teams refresh weekly into a warehouse.

Call /v1/{customer}/reports:countInstalledApps and return the top 25 extensions sorted by user count.

Fleet Version and Crash Reporting

IT teams monitor Chrome version drift and crash trends across thousands of managed devices. countChromeVersions returns the version distribution and countChromeCrashEvents groups crashes by version and reason, so admins can detect regressions in a specific minor release before user reports come in. Reports are aggregate counts - no PII is required.

Call /v1/{customer}/reports:countChromeCrashEvents grouped by chrome_version for the last 14 days and return the top 5 versions by crash count.

ChromeOS Device Lifecycle Planning

Procurement teams use countChromeDevicesReachingAutoExpirationDate to plan refresh cycles, identifying ChromeOS devices losing automatic updates within a chosen horizon. The API returns aggregated counts grouped by model and expiration date, which supports budget forecasting without exporting device-level CSVs from the admin console.

Call /v1/{customer}/reports:countChromeDevicesReachingAutoExpirationDate for devices expiring in the next 12 months and return counts by model.

AI Agent IT Reporter via Jentic

An AI agent through Jentic builds an on-demand IT report - Chrome version drift, top crash signatures, devices reaching end-of-life, and the most-requested extensions - without the admin having to navigate the Chrome Management console. Jentic isolates the Workspace OAuth credentials and exposes the report endpoints as named tools.

Through Jentic, search chromemanagement_count_chrome_versions, load schema, and execute it for customer C0123 over the last 30 days.

Key Endpoints

22 endpoints — the chrome management api gives workspace and chromeos administrators programmatic access to managed-browser and chromeos device telemetry, app and extension inventories, version distribution, crash events, and printing reports.

METHOD

PATH

DESCRIPTION

GET

/v1/{+customer}/reports:countChromeVersions

Count Chrome browsers by version

GET

/v1/{+customer}/reports:countChromeCrashEvents

Count Chrome crash events

GET

/v1/{+customer}/reports:countInstalledApps

Count installed apps and extensions

GET

/v1/{+customer}/apps:fetchUsersRequestingExtension

List users requesting a specific extension

GET

/v1/{+customer}/reports:countChromeDevicesReachingAutoExpirationDate

Count devices reaching auto-update expiration

GET

/v1/{+customer}/reports:countPrintJobsByPrinter

Summarise print jobs by managed printer

GET

/v1/{+customer}/reports:countChromeVersions

Count Chrome browsers by version

GET

/v1/{+customer}/reports:countChromeCrashEvents

Count Chrome crash events

GET

/v1/{+customer}/reports:countInstalledApps

Count installed apps and extensions

GET

/v1/{+customer}/apps:fetchUsersRequestingExtension

List users requesting a specific extension

GET

/v1/{+customer}/reports:countChromeDevicesReachingAutoExpirationDate

Count devices reaching auto-update expiration

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Workspace OAuth credentials with chrome.management scopes are stored once, encrypted, by your own Jentic One instance and injected at execution time. The agent receives only short-lived access tokens and the refresh token never enters its prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list installed Chrome extensions across the fleet', and Jentic returns the matching reports operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Chrome Management API through Jentic.

What authentication does the Chrome Management API use?

It requires OAuth 2.0 with the chrome.management.reports.readonly or chrome.management.appdetails.readonly scopes on a Workspace super admin or delegated admin account. Through Jentic, the OAuth credential is stored encrypted in your Jentic One instance and the agent receives only short-lived scoped access tokens.

Can I list every Chrome extension installed across our fleet?

Yes. Call /v1/{customer}/reports:countInstalledApps to get aggregate counts by extension and complement it with /v1/{customer}/apps:fetchUsersRequestingExtension to identify which users requested a specific extension.

What are the rate limits for the Chrome Management API?

Google enforces a per-project per-minute quota of around 600 read requests and lower limits for fleet-wide aggregations. Use orderBy and pageSize to keep responses small and stay within quota when reporting across very large fleets.

How do I report on Chrome crashes through Jentic?

Use the Jentic search query "count Chrome crash events" to discover the customers.reports.countChromeCrashEvents operation, load its schema, and execute it with the customer id and a time range. Run pip install jentic to get started.

Does the API expose per-device crash details?

Counts are aggregated by version, browser channel, or OS for privacy reasons. Per-device crash detail is not exposed through this API - use the Chrome Management console or Telemetry events for richer drill-down.

Is the Chrome Management API free?

It is included with Chrome Enterprise Upgrade and ChromeOS Enterprise licences. There is no per-call charge from Google for the report endpoints used by this API.

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

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and the customer id sits in every path (for example /v1/{customer}/reports:countChromeVersions), so a rule can pin the agent to one customer's Chrome and ChromeOS telemetry and nothing else. Every operation here, from countInstalledApps and countChromeCrashEvents to fetchUsersRequestingExtension, is read-only, so even with access the agent can report on inventory, versions, and crashes but cannot change any device configuration. You can also allow only the specific report and app operations the agent needs and withhold the rest.