How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Google Chrome Telemetry Notification Configs API

Operations for managing telemetry notification configurations that enable push notifications for telemetry events.

Google Chrome Telemetry Notification Configs API is one of 15 APIs that Google Chrome publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Telemetry Notification Configs. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, code examples, and a GitHub repository.

This API exposes 3 operations across 2 paths, and defines 3 schemas. It is described by OpenAPI 3.1.0, at version v1.

Requests are made against a single base URL, https://chromemanagement.googleapis.com/v1.

3 operations 2 paths 3 schemas 1 DELETE1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
v1
Server
https://chromemanagement.googleapis.com/v1
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Google Chrome Telemetry Notification Configs API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 3 scopes. By default, every request must be authenticated.

  • oauth2 — Google OAuth 2.0 authentication. Requires appropriate Chrome Management API scopes.

Paths & Operations 3

Across 2 paths, the API surfaces 3 operations — 1 DELETE, 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Telemetry Notification Configs 3

Operations for managing telemetry notification configurations that enable push notifications for telemetry events.

GET
/customers/{customerId}/telemetry/notificationConfigs
List telemetry notification configs
listTelemetryNotificationConfigs 3 params → 200
POST
/customers/{customerId}/telemetry/notificationConfigs
Create a telemetry notification config
createTelemetryNotificationConfig 1 param body → 200400
DELETE
/customers/{customerId}/telemetry/notificationConfigs/{configId}
Delete a telemetry notification config
deleteTelemetryNotificationConfig 2 params → 200404

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are TelemetryNotificationConfig (4 properties), GoogleRpcStatus (3 properties), ListTelemetryNotificationConfigsResponse (2 properties). Each schema is shown below with its type and property counts.

ListTelemetryNotificationConfigsResponse
object
Response containing a list of telemetry notification configurations.
2 properties
TelemetryNotificationConfig
object
Configuration for telemetry push notifications.
4 properties
GoogleRpcStatus
object
Standard Google API error response following the google.rpc.Status format.
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

google-chrome-telemetry-notification-configs-api-openapi.yml Raw ↑

Other APIs Google Chrome publishes across the network.

Chrome Extensions API
Chrome DevTools Protocol
Chrome Web Store API
Chrome User Experience Report API
Chrome Policy API
Chrome Verified Access API
Google Safe Browsing API
PageSpeed Insights API
Chrome Built-in AI APIs
Google Chrome App Details API
Google Chrome Reports API
Google Chrome Telemetry Devices API
Where this information came from

This is an independent, third-party profile of Google Chrome Telemetry Notification Configs API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.