Google APIs

274 APIs7,055 Endpoints22 Categories

API Catalog(29 of 274)

Analytics Hub API

Analytics Hub is Google Cloud's data exchange built on top of BigQuery. The API manages data exchanges, listings (the published shareable assets), and subscriptions (the consumer side that surfaces a listing in a destination project's BigQuery dataset). It supports listing, creating, subscribing, refreshing, and revoking these resources, plus IAM-style policy management on each. It is intended for organisations that publish or consume data products across project, team, or organisation boundaries.

16 endpoints

Analytics Reporting API

The Analytics Reporting API v4 is the advanced reporting surface for Universal Analytics. Compared to Google Analytics v3 Core Reporting, v4 introduced batched report requests, segments, cohort reports, pivots, and richer date range support in a single endpoint. With Universal Analytics no longer processing new data after July 2023, this API is now used to read historical UA data with the v4 feature set, and for the userActivity:search endpoint that returns the activity history of a single user. New reporting work should target the GA4 Data API.

2 endpoints

BigQuery API

BigQuery is Google Cloud's serverless data warehouse for running SQL analytics over petabyte-scale datasets without managing infrastructure. The API exposes datasets, tables, jobs, models, routines, and row access policies so you can load data, run queries, stream inserts, schedule extracts, and manage ML routines from code. It supports federated queries across Cloud Storage, Bigtable, and external sources, and integrates with Google's IAM for fine-grained access control. Pricing is consumption-based on bytes scanned plus storage, with flat-rate reservations available for predictable workloads.

42 endpoints

BigQuery Connection API

The BigQuery Connection API manages named connection resources that BigQuery uses to query external data sources such as Cloud SQL, Spanner, AWS, and Azure without copying the data. You can create connections, attach IAM policies, and reference them from federated queries and external tables in BigQuery. This is the control-plane API for federation; the connections it creates are then used by the main BigQuery query engine. Each connection isolates credentials for the underlying source so analysts can query across systems without holding direct database secrets.

8 endpoints

BigQuery Data Transfer API

The BigQuery Data Transfer Service automates recurring data loads into BigQuery from SaaS applications (Google Ads, Campaign Manager, YouTube, Search Ads), other clouds (S3, Azure Blob), and Cloud Storage. The API exposes data sources, transfer configurations, runs, and transfer logs so you can enroll sources, schedule transfers, backfill historical windows, and monitor failures. Each transferConfig holds a schedule, destination dataset, and source-specific parameters. This is the right plane when the use case is 'land this source in BigQuery on a cadence' rather than ad-hoc loads.

14 endpoints

BigQuery Reservation API

The BigQuery Reservation API manages flat-rate compute capacity for BigQuery: capacityCommitments buy slots for a term, reservations group those slots, and assignments bind reservations to projects, folders, or organisations. The API also supports failover, splitting and merging commitments, and searching assignments. Teams use this when on-demand pricing becomes volatile and they want predictable, reserved slot capacity. It does not run queries; it controls how the capacity that runs queries is allocated.

15 endpoints

Business Profile Performance API

The Google Business Profile Performance API exposes daily and monthly performance metrics for verified Business Profile locations, covering search impressions, map views, calls, direction requests, website clicks, and search-keyword impressions. It is designed for multi-location operators, agencies, and analytics platforms that need to ingest Business Profile insights at scale rather than read them from the Business Profile Manager UI. The current v1 surface is small and tightly scoped — three reporting endpoints — but covers the metrics most retailers and service businesses care about.

3 endpoints

Chrome UX Report API

The Chrome UX Report (CrUX) API exposes aggregated, anonymised real-user performance data collected from Chrome users for any sufficiently popular public origin or page URL. It returns Core Web Vitals — Largest Contentful Paint, Interaction to Next Paint, Cumulative Layout Shift — plus First Contentful Paint, Time to First Byte, and form-factor splits. Performance teams use it to track field metrics for sites they own and benchmark competitors' real-user performance.

2 endpoints

Cloud Data Fusion API

Cloud Data Fusion is a fully-managed, cloud-native data integration service for building and operating ETL/ELT pipelines through a graphical pipeline designer. The API exposes 15 endpoints that provision and lifecycle Data Fusion instances, manage DNS peerings, and inspect available platform versions. It is the control-plane API: pipeline design and execution happen inside the instance UI and the per-instance CDAP REST API.

15 endpoints

Cloud Dataplex API

Cloud Dataplex is Google's data lake management service: it organises data spread across BigQuery, Cloud Storage, and other sources into governed lakes, zones, and assets. The API exposes 53 endpoints covering lakes and zones, content (notebooks and SQL scripts), data scans for quality and profiling, data taxonomies and policies, plus a unified entry-and-aspect catalog for metadata search. Agents and platform teams use it to enforce governance and discover data without standing up a separate metadata store.

53 endpoints

Cloud Dataproc API

Cloud Dataproc is Google's managed Hadoop and Spark service for running batch, streaming, and interactive analytics workloads. The API exposes 65 endpoints covering clusters, jobs, workflow templates, autoscaling policies, batches (serverless Spark), and sessions (interactive Jupyter). It supports cluster create-start-stop-repair lifecycle plus job submission for Spark, PySpark, Hive, Pig, Presto, and SparkR engines.

65 endpoints

Contact Center AI Insights API

Google Contact Center AI Insights API turns recorded customer conversations into structured analytics. It ingests audio or transcript files, runs speaker diarisation, transcription, sentiment, entity, and topic detection, and surfaces the results as conversation, analysis, and issue model resources. Operators can build issue models that auto-classify calls, extract phrase matchers and smart highlighters, and run aggregate metric queries across millions of conversations. The API is region-scoped and supports both batch upload and streaming ingestion patterns.

45 endpoints

Data pipelines API

The Google Cloud Data pipelines API offers a thin scheduling layer over Dataflow templates, letting teams create, list, run, and stop recurring data analytics pipelines. It exposes 8 endpoints scoped to pipelines and their job history, with a built-in cron-style schedule on each pipeline. Pipelines are backed by Dataflow batch and streaming jobs, but this API removes the need to schedule them through Cloud Scheduler or Composer.

8 endpoints

Dataflow API

Google Cloud Dataflow API is the control plane for streaming and batch Apache Beam pipelines on Google Cloud. It exposes endpoints to launch jobs from Flex or classic templates, list and inspect jobs and their workers, drain or cancel running streaming jobs, and update the parameters of in-flight pipelines. The API also surfaces job metrics, debug snapshots, and template metadata so platform teams can build dashboards and self-service launchers without bespoke Beam code. Jobs run on managed worker VMs in the chosen region, with autoscaling controlled per job.

41 endpoints

Dataform API

The Dataform API lets you develop, version-control, and operationalize SQL pipelines that run inside BigQuery. It manages repositories, workspaces, release configurations, compilation results, and workflow invocations so teams can ship reproducible SQL transformations through Git-backed workflows. The API exposes 43 endpoints covering Git operations (commit, push, pull, fetch history), workspace file editing, and scheduled workflow execution against BigQuery.

43 endpoints

Datastream API

Google Cloud Datastream is a serverless change-data-capture (CDC) and replication service that streams changes from operational databases (Oracle, MySQL, PostgreSQL, SQL Server) into BigQuery, Cloud Storage, and other destinations. The API exposes 21 endpoints covering connection profiles for source and destination, streams, private connectivity for VPC peering, and routes. It supports continuous replication with backfill, schema discovery, and per-stream pause/resume.

21 endpoints

Firebase Cloud Messaging Data API

The Firebase Cloud Messaging Data API exposes aggregated delivery metrics for FCM push notifications sent to Android applications. It returns daily-aggregated counts of message attempts, deliveries, and failure reasons broken down by analytics labels and droppage causes. Use it to understand notification health, diagnose drops caused by quota or device state, and feed delivery data into product analytics dashboards.

1 endpoints

Gmail Postmaster Tools API

The Gmail Postmaster Tools API gives high-volume senders programmatic access to deliverability metrics that were previously only viewable in the Postmaster Tools UI. Senders can pull spam rates, IP and domain reputation, authentication results (SPF, DKIM, DMARC), feedback loop identifiers, and delivery error breakdowns for domains they have verified. The data is aggregated daily and is intended to help senders diagnose deliverability problems before they become reputation-damaging. The API exposes domain registration metadata along with per-day traffic statistics for each verified sending domain.

3 endpoints

Google Analytics Admin API

The Google Analytics Admin API is the configuration surface for GA4 properties. It manages accounts, properties, data streams (web, iOS, Android), conversion events, custom dimensions and metrics, and the user access bindings on those resources. It also exposes provisioning of new accounts via account tickets, change history search, and access reports for compliance review. It is the management plane for GA4; reporting goes through the Google Analytics Data API.

28 endpoints

Google Analytics API

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.

88 endpoints

Google Analytics Data API

The Google Analytics Data API is the reporting surface for GA4 properties. It runs custom reports with dimensions and metrics, batched reports across several queries, pivot reports, real-time reports, and on-demand audience exports. It also exposes a metadata endpoint that lists every dimension and metric available on a property and a checkCompatibility call that explains why a particular dimension/metric combination is not allowed. Reporting only — property configuration goes through the Admin API.

10 endpoints

Google Cloud Data Catalog API

Google Cloud Data Catalog API is a fully managed metadata service for discovering, describing, and governing data assets across BigQuery, Pub/Sub, Cloud Storage, and external sources. It exposes catalog search, entry groups, entries, tag templates, and tags so that data stewards can attach business context to columns and tables. Search supports keyword, fully qualified name, and metadata filter syntax. The API also handles IAM at every level so that data discovery can be opened to analysts while edits remain restricted to stewards.

35 endpoints

Google Play Developer Reporting API

The Google Play Developer Reporting API gives Android app developers programmatic access to the same vitals, errors, and anomaly data that appear in Play Console. Across 7 endpoints it exposes searchable apps, queryable metric sets such as crash rate and ANR rate, error issue search, anomaly listing, and release-filter option fetching. Developers can build dashboards, alerting pipelines, and post-release health checks without scraping Play Console.

7 endpoints

Google Play Grouping API

The Google Play Grouping API lets Android apps tag in-app users with custom attributes that Play Console can then use as audience filters in vitals reports, store listing experiments, and notifications. Two endpoints cover verifying that a token belongs to a Play user and creating or updating tags on that user, all keyed by an opaque app-issued token. The intended flow is server-side: an app's backend mints tags such as 'beta_cohort' or 'high_lifetime_value' so Play tooling can segment vitals and messaging on those attributes.

2 endpoints

Looker (Google Cloud core) API

The Looker (Google Cloud core) API manages the lifecycle of Looker instances hosted as a Google Cloud service, including provisioning, restart, import, export, and deletion. It is the control-plane API for Looker on Google Cloud, distinct from Looker's own SDK that handles dashboards, looks, and queries. Operations are long-running, returning operation handles that can be polled or cancelled, and instances are scoped to project locations.

11 endpoints

PageSpeed Insights API

The PageSpeed Insights API runs Lighthouse against any public URL and returns a structured performance report including Core Web Vitals, lab metrics, and optimisation suggestions. It exposes a single runPagespeed endpoint that accepts a URL plus options for strategy (mobile or desktop) and the categories to score (performance, accessibility, best-practices, SEO, PWA). Use it to integrate web performance budgets into CI, build dashboards that track real-user metrics over time, or pull suggestions to feed engineering backlogs. The spec exposes 1 endpoint.

1 endpoints

Tag Manager API

The Google Tag Manager API gives programmatic access to GTM accounts, containers, workspaces, tags, triggers, variables, environments, and version history. It lets ops and analytics teams script tag deployments, audit container configurations, replicate environments across properties, and publish container versions without using the GTM web UI. Every change made through the API is captured in workspace history and can be promoted through environments for staged rollouts.

55 endpoints

YouTube Analytics API

The YouTube Analytics API exposes channel and content performance data for the authorised YouTube account. It supports targeted reports — views, watch time, subscribers gained, demographics, traffic sources — driven by metric, dimension, and filter parameters, plus group and groupItem management to roll multiple videos or channels into named cohorts. This is the API for live, ad-hoc analytics queries; bulk historical exports use the separate YouTube Reporting API.

8 endpoints

YouTube Reporting API

The YouTube Reporting API schedules and downloads bulk CSV reports of YouTube channel and content analytics. Clients pick a reportType, create a recurring job, and pull the daily report files generated against the authorised channel. This is the right API for warehousing, backfilling, and large-scale analytics work where parameterised live queries are impractical; YouTube Analytics handles the ad-hoc, real-time use case.

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