Chrome Version History API

Name: Chrome Version History API API
Brand: Chrome Version History API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsMonitoring ObservabilityapiKey4 EndpointsREST

For Agents

Look up Chrome release channels, platforms, releases, and versions so an agent can pin tests, alert on new builds, or generate compatibility reports.

Quickstart

Get started with Chrome Version History API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"find the current chrome stable version"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Chrome Version History API API.

List the available Chrome release channels including Stable, Beta, Dev, and Canary

Enumerate the platforms Chrome ships on, from Windows and Mac to Android and iOS

Look up every release event for a channel and platform with promotion dates

Retrieve specific Chrome versions with version strings and build identifiers

GET STARTED

Start building with Chrome Version History API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Chrome Version History API API for, with concrete tasks.

★ Browser Compatibility Test Pinning

QA and release teams pin browser automation jobs to specific Chrome versions to keep test results reproducible across CI runs. The Version History API returns the canonical version strings per channel and platform, which the test harness uses to download the matching ChromeDriver and Chrome binary. This eliminates drift caused by silent Chrome auto-updates and gives test failures a stable version coordinate.

Get the current Stable Chrome version on Linux and emit it to the CI environment for ChromeDriver matching

Release Monitoring and Alerting

Web platform teams subscribe to a polling job that calls the Version History API hourly and alerts when a new Stable or Beta release has been promoted on production-relevant platforms. The releases endpoint returns promotion timestamps so the alert payload can include both the version number and the rollout date. This replaces the need to scrape the Chrome status dashboard.

List the latest Stable releases on Windows and notify Slack if the most recent timestamp is within the last 24 hours

Compatibility Documentation and Reporting

Developer relations and documentation teams generate compatibility tables that show when a Chrome feature shipped to Stable on each platform. The Version History API supplies the historical release timeline, letting docs render charts that stay in sync with the actual Chrome release cadence. The data is fully read-only and unauthenticated, so docs can call it from public CI pipelines.

List every Stable release on Mac for the past year and produce a markdown table of versions and dates

AI Agent Browser Tooling Helper

An AI agent integrated through Jentic answers prompts like 'what version of Chrome should I test against?' by discovering the Version History API by intent search, calling the releases endpoint for the requested channel and platform, and returning the most recent version with its promotion date. Because the API requires only a Google API key, Jentic stores the key in the MAXsystem vault and exposes a scoped reference at execution time.

Search Jentic for chrome stable version and call the releases endpoint for win64 Stable

Key Endpoints

4 endpoints — the chrome version history api exposes the same release data that powers the chrome version dashboard, enabling automation that reads channels, platforms, releases, and individual versions.

METHOD

PATH

DESCRIPTION

GET

/v1/{+parent}/channels

List Chrome release channels

GET

/v1/{+parent}/platforms

List supported platforms

GET

/v1/{+parent}/versions

List Chrome versions for a parent channel and platform

GET

/v1/{+parent}/releases

List release events with promotion timestamps

GET

/v1/{+parent}/channels

List Chrome release channels

GET

/v1/{+parent}/platforms

List supported platforms

GET

/v1/{+parent}/versions

List Chrome versions for a parent channel and platform

GET

/v1/{+parent}/releases

List release events with promotion timestamps

Why though Jentic?

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

Credential isolation

Chrome Version History API keys are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — the raw Google API key never enters the agent's context, even though the API is read-only and the key is mainly used for quota attribution.

Intent-based discovery

Agents search Jentic with intents like 'find the current chrome stable version' and Jentic returns the releases endpoint with its full input schema, including the parent path format, so the agent can construct a valid request without reading Google's discovery doc.

Time to first call

Direct Version History integration: half a day for endpoint wiring and parent-path templating. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Chrome Management API

Manage the Chrome browser fleet whose versions Version History reports

Choose Chrome Management when an agent needs to enroll or configure managed Chrome devices; pair with Version History to see what version they should be on.

Complementary

Chrome Policy API

Set Chrome update and channel policies for managed devices

Choose Chrome Policy when an agent needs to control the channel a fleet is pinned to; pair with Version History to verify the rollout.

Complementary

Cloud Monitoring API

Emit alerts when Version History reports a new Stable promotion

Choose Monitoring when an agent needs to fan out alerts on new Chrome releases through existing Cloud Monitoring channels.

FAQs

Specific to using Chrome Version History API API through Jentic.

What authentication does the Chrome Version History API use?

The Chrome Version History API accepts an unauthenticated read for public data and supports an optional Google API key passed as the api_key query parameter to attribute usage to a Cloud project. Through Jentic, the API key is stored encrypted in the MAXsystem vault and only a scoped reference is exposed to the agent.

Can I get the current Chrome Stable version with the Chrome Version History API?

Yes. Call GET /v1/chrome/platforms/{platform}/channels/stable/versions to list current Stable versions for a platform such as win64, mac, or linux. The first entry is the most recently shipped Stable build with its full version string.

What are the rate limits for the Chrome Version History API?

Google enforces standard Cloud per-project quotas on Version History with a default of about 600 requests per minute per project. Anonymous unauthenticated callers are subject to per-IP throttling that is lower but unspecified; high-volume callers should attach a Cloud project API key.

How do I monitor new Chrome releases through Jentic with the Version History API?

Install Jentic with pip install jentic, search for chrome stable version, load the schema for the releases endpoint, and run it on a schedule against the channel and platform you care about. Compare the most recent serving timestamp to your last seen value and trigger an alert when it advances.

Does the Chrome Version History API include ChromeOS and mobile versions?

Yes. The platforms endpoint returns ChromeOS, Android, iOS, Windows, Mac, and Linux entries. You can request versions and releases under any platform, though the channel availability differs (for example, ChromeOS exposes the LongTermSupport channel that desktop platforms do not).

Why does my Version History query return an empty versions list?

Empty results usually indicate an unsupported channel-platform combination or a malformed parent path. Use GET /v1/chrome/platforms/{platform}/channels to list valid channels for that platform before requesting versions or releases.