Google APIs

274 APIs7,055 Endpoints22 Categories

API Catalog(30 of 274)

Accelerated Mobile Pages (AMP) URL API

The Accelerated Mobile Pages (AMP) URL API resolves a batch of canonical web URLs into their AMP equivalents and the corresponding Google AMP Cache URLs. It returns the AMP variant for each input URL when one is published or an explanatory error when no AMP version exists. Search teams and content distributors use it to programmatically pre-fetch or display AMP pages from a list of canonical URLs.

1 endpoints

API Discovery Service

Google's API Discovery Service is the meta-API that describes every other Google API. Two endpoints expose the directory of supported APIs and the machine-readable Discovery REST description for each one — methods, parameters, schemas, scopes, and base URLs. Client library generators, IDE tooling, and Jentic itself use this surface to bootstrap integrations against the entire googleapis.com surface without hand-written specs.

2 endpoints

Apigee API

The Apigee API is the control plane for Google Cloud's enterprise API management platform. It exposes operations to develop and secure API proxies, deploy and undeploy proxy revisions, monitor traffic, configure environments and instances, manage developer apps and API products, and run analytics and monetization workflows. Resources include organizations, environments, API proxies, shared flows, target servers, key value maps, and developer portals.

130 endpoints

Apigee Registry API

The Apigee Registry API stores, versions, and indexes API descriptions and machine-readable specs in a Google Cloud project. It models APIs, ApiVersions, ApiSpecs, ApiDeployments, and Artifacts as first-class resources, exposes revisions and rollback for specs, and supports artifact storage for governance metadata such as scorecards and lint reports. It works alongside Apigee runtime but does not depend on it.

26 endpoints

App Hub API

The Google Cloud App Hub API gives platform teams a single inventory of the applications running across their Google Cloud organization. It models Applications composed of Services and Workloads, with Service Project Attachments that bind compute projects to the central host, and DiscoveredServices and DiscoveredWorkloads that surface what is actually running. App Hub becomes the source of truth for application ownership, criticality, and environment.

23 endpoints

Apps Script API

The Google Apps Script API manages and executes Google Apps Script projects programmatically, including project creation, content updates, deployments, versions, and execution metrics. It exposes endpoints for retrieving and updating script content, listing and creating versions and deployments, and enumerating script processes and metrics so operators can build CI/CD pipelines around Apps Script. The API enables external systems to deploy and monitor Apps Script automations that extend Google Workspace and Google Sheets.

16 endpoints

Artifact Registry API

The Artifact Registry API is Google Cloud's managed service for storing and serving build artifacts including Docker container images, Maven, npm, Python, apt, and yum packages. It exposes operations to manage repositories, list and download package versions, attach files, and import artifacts from supported source formats. Repositories are scoped to a project and location, and access is governed by Cloud IAM roles bound to the registry resource. The API is the single integration surface for CI pipelines, Cloud Build, and Cloud Run when promoting and consuming versioned artifacts.

34 endpoints

Blockchain Node Engine API

Blockchain Node Engine is Google Cloud's managed Ethereum-compatible node service. The API provisions and manages dedicated archive and full nodes that you can query via JSON-RPC for on-chain data, transaction submission, and indexing without operating execution and consensus client pairs yourself. The API exposes blockchainNodes resources plus the surrounding long-running operations and locations metadata. It targets teams building wallets, indexers, analytics, and dApp backends that need a stable RPC endpoint with Google's reliability and IAM model.

8 endpoints

Chrome Management API

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. It is the read API behind the Chrome Management console — useful for building cross-cloud reporting, enforcing extension allowlists, or tracking devices reaching end-of-life. Most operations are scoped to a customer id and aggregate counts across the managed fleet.

22 endpoints

Chrome Version History API

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. Tooling can identify the current Stable, Beta, Dev, and Canary versions per platform, see when each version was promoted, and pin compatibility tests to known release builds. The API is read-only and unauthenticated for public release data.

4 endpoints

Cloud Build API

Google Cloud Build is a managed continuous-integration service that compiles source code, runs tests, and produces container images or other artifacts on Google Cloud. The API exposes builds, build triggers, worker pools, and GitHub webhook integration so agents can launch builds on demand, configure triggers that fire on Git events, and inspect build logs and status. Builds run in isolated VMs with configurable machine size and private worker pools for builds that need access to internal networks.

40 endpoints

Cloud Composer API

Cloud Composer is Google Cloud's managed Apache Airflow service. The API provisions and manages Composer environments, runs Airflow CLI commands remotely, polls long-running command output, triggers database failover, snapshots an environment, and manages user workloads on the underlying GKE cluster. It is the orchestration backbone for ETL, ML pipelines, and cross-system workflows that need scheduled DAG execution without standing up Airflow infrastructure.

21 endpoints

Cloud Deploy API

Google Cloud Deploy is a managed, opinionated continuous-delivery service that promotes container images and Kubernetes manifests through a series of target environments such as staging and production. The API exposes delivery pipelines, releases, rollouts, targets, and approval steps so agents can promote a release to the next stage, abandon a release, approve a pending rollout, or roll back to a previous successful deployment. Cloud Deploy integrates with Cloud Build for build artefacts and with GKE, Cloud Run, and Anthos for deployment targets.

32 endpoints

Cloud Logging API

Cloud Logging is Google Cloud's centralised log management service for writing, storing, searching, and routing log entries from applications, virtual machines, containers, and Google Cloud services. It supports structured and unstructured logs, log-based metrics, exclusion filters, and sinks that route entries to BigQuery, Pub/Sub, or Cloud Storage. Log Buckets and views provide retention control and tenant-level access, while CMEK settings let teams bring their own encryption keys for compliance workloads.

47 endpoints

Cloud Monitoring API

Cloud Monitoring is Google Cloud's observability service for collecting, querying, and alerting on metrics, with support for uptime checks and notification channels. The v3 API exposes time series, metric and monitored resource descriptors, alert policies, notification channels, groups, and uptime check IPs and configs. It pairs with Cloud Logging for full observability and supports Prometheus-compatible queries through monitored projects scoped to a Workspace.

32 endpoints

Cloud Profiler API

Google Cloud Profiler is a managed continuous-profiling service that gathers CPU and heap profiles from production applications with negligible overhead. The API is small and primarily agent-facing: profiling agents embedded in applications call createProfile to register a profiling session, then upload sampled profile data via patch operations. Offline reporting tools use createOfflineProfile to submit profile data captured outside Google Cloud, allowing the same flame-graph and comparison tooling to surface non-GCP workloads.

4 endpoints

Cloud Runtime Configuration API

The Cloud Runtime Configuration API exposes the Runtime Configurator, which lets services dynamically configure and share variables across Google Cloud workloads. It supports configs as containers, variables as named values, and waiters that block until a condition over those variables is met or a timeout elapses. The API also provides a watch endpoint that returns when a single variable changes, plus IAM endpoints to control who can read or update each config.

13 endpoints

Cloud Scheduler API

Cloud Scheduler is a fully managed enterprise-grade cron service for Google Cloud. The API lets you create, update, pause, resume, and run jobs that fire HTTP, App Engine, or Pub/Sub targets on a recurring schedule defined with standard cron syntax. It handles retries with exponential backoff and reports per-job execution state, replacing fragile self-hosted cron servers for batch ETL, billing rollups, and timed agent workflows.

10 endpoints

Cloud Shell API

The Cloud Shell API lets users start, configure, and connect to interactive shell sessions running on Google-managed VMs preloaded with the gcloud SDK and common developer tooling. Programmatic callers can fetch the user's environment, authorize an SSH session, and manage the public keys used to connect from local clients. It is most often used to embed a one-click shell experience into developer tools, training apps, and onboarding flows that need a real Linux environment without provisioning infrastructure.

7 endpoints

Cloud Source Repositories API

The Cloud Source Repositories API manages private Git repositories hosted in a Google Cloud project. It provides operations to create and delete repos, list the repos within a project, mirror an existing GitHub or Bitbucket repository, and manage IAM policies that govern who can push, pull, or administer each repository. The API also exposes project-level Pub/Sub mirroring configuration, useful when triggering CI builds from repository activity.

11 endpoints

Cloud Testing API

Cloud Testing API drives Firebase Test Lab, Google's managed mobile-app testing infrastructure. Submit Android APKs or iOS XCTest archives plus instrumentation and Robo test specifications, and Test Lab runs them on a matrix of physical and virtual device models, OS versions, locales, and orientations. The API exposes the test environment catalog (which devices and APIs are available), submits test matrices, and reports back execution status. Pairs with Cloud Tool Results API to retrieve detailed logs, screenshots, and video recordings.

10 endpoints

Cloud Tool Results API

Cloud Tool Results stores and serves the detailed output of Firebase Test Lab runs and other Google developer-tooling executions. Results are organised hierarchically as histories (one per app), executions (one per matrix run), steps (one per device-execution combination), and per-step artefacts including logcat, screenshots, video, performance metrics, and test-case results. The API is the backbone behind the Firebase Test Lab UI in the Google Cloud Console and is what teams call when they need programmatic access to deep test diagnostics.

29 endpoints

Cloud Trace API

Cloud Trace is Google Cloud's distributed tracing backend. The v2 API accepts trace spans from instrumented applications via a single batchWrite endpoint and exposes a span create endpoint, while collected traces are queryable through the Cloud Trace UI and the broader observability stack. App Engine applications send trace data automatically; other workloads push spans through this API or via OpenTelemetry exporters that hit the same endpoints.

2 endpoints

Error Reporting API

Google Cloud Error Reporting groups similar errors emitted by applications and services running on Google Cloud, surfacing each unique error as a group with counts, first/last seen timestamps, and example stack traces. The API lets agents report new errors directly, list error groups with statistics, list individual error events for a group, and update group metadata such as the resolution status. It is commonly paired with Cloud Logging-based ingestion for languages and runtimes that surface errors automatically.

6 endpoints

Firebase App Distribution API

The Firebase App Distribution API automates pre-release distribution of iOS and Android binaries to internal testers, QA teams, and beta groups. It exposes operations to upload release binaries, distribute releases to tester groups, manage testers and groups, and track upload long-running operations. Use it to wire up CI pipelines so each merge produces a build automatically delivered to the right tester group without manual TestFlight or Play Console steps.

18 endpoints

Firebase Management API

The Firebase Management API enables programmatic setup and lifecycle management of Firebase projects and the iOS, Android, and Web apps registered inside them. It exposes operations to add Firebase to an existing Google Cloud project, register apps, list available locations, fetch SDK config, and manage SHA certificate fingerprints for Android apps. Use it to automate project provisioning across environments without clicking through the Firebase console.

21 endpoints

Google Play Android Developer API

The Google Play Android Developer API lets app developers manage their Google Play presence programmatically. The expected workflow is to insert an Edit, make changes (uploading APKs, AABs, listings, screenshots, release tracks), and commit the Edit to publish. The API also covers in-app product and subscription management, voided purchases, app recoveries, internal app sharing artifacts, data safety declarations, and device tier configurations.

112 endpoints

Google Play Custom App Publishing API

The Google Play Custom App Publishing API lets enterprise app developers publish private Android apps directly to specific managed Google Play organisations without going through the public store review queue. The single endpoint creates a custom app under a developer account and associates it with one or more enterprise organisation IDs, returning the package name and Play Console identifiers needed for subsequent uploads. It is intended for managed-Google-Play customers who distribute internal-only Android binaries to employees.

1 endpoints

Google Play EMM API

The Google Play EMM API lets enterprise mobility management providers deploy, license, and manage apps on Android Enterprise devices. EMM partners use it to enroll enterprises, distribute managed Google Play apps, push web apps, manage app permissions and licenses, and configure managed device policies. The API also covers store layouts, product approvals, service accounts, and notification pulls for near-real-time device state updates.

77 endpoints

Remote Build Execution API

The Google Remote Build Execution API administers RBE instances and worker pools used to scale Bazel and other Remote Execution-API-compatible builds across distributed worker fleets. It supports creating, listing, updating, and deleting RBE instances, configuring worker pools that supply the build farm, and managing IAM bindings that govern who can submit work. Specialized create endpoints exist for AndroidCI, Kokoro, and Guitar instances, alongside a notification-test endpoint for verifying alert delivery.

13 endpoints

Connect Your Agent

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.