Google APIs

274 APIs7,055 Endpoints22 Categories

API Catalog(34 of 274)

Abusive Experience Report API

The Abusive Experience Report API exposes Google's findings on sites that show abusive experiences such as fake messages, deceptive ads, and unexpected redirects. It returns the abusive status (Failing, Passing, or Not Reviewed) for a single site and a list of all sites currently failing the report. Publishers and ad-quality teams use it to monitor whether their domains are at risk of having Chrome filter abusive ads.

2 endpoints

Access Approval API

The Access Approval API gives Google Cloud customers explicit control over when Google personnel can access their data. It exposes operations to configure approval settings on a project, folder, or organisation, list pending approval requests, and approve, dismiss, or invalidate each request. Compliance and security teams use it to satisfy regulatory requirements that demand documented, customer-approved access by the cloud provider's support staff.

7 endpoints

Access Context Manager API

The Access Context Manager API lets Google Cloud organisations define attribute-based access controls on requests to Google Cloud services. It exposes operations to manage access policies, access levels (boolean expressions over device, IP, and identity attributes), and service perimeters that restrict data movement between projects. Security and platform teams use it to enforce zero-trust controls and to build VPC Service Controls perimeters around regulated workloads.

22 endpoints

API Keys API

The Google Cloud API Keys API manages the API keys associated with developer projects. It exposes operations to create, retrieve, update, delete, and undelete keys, look up a key by string, and fetch the key string itself. API keys can be restricted by API target, IP address, HTTP referrer, or Android and iOS application identifiers, giving teams least-privilege credentials for unauthenticated services.

8 endpoints

Assured Workloads API

The Assured Workloads API programmatically manages Google Cloud's compliance-controlled folders that enforce regulatory regimes such as FedRAMP, IL4, CJIS, and EU Sovereign Controls on the resources created inside them. It exposes operations to create and update workloads, restrict allowed resource types and locations, mutate partner-controlled permissions, and acknowledge violations surfaced by the platform. Workload state changes are returned as long-running operations that callers must poll for completion. The API is the control-plane for compliance posture, not for building or running the underlying applications.

12 endpoints

BigQuery Data Policy API

The BigQuery Data Policy API manages column-level masking policies that BigQuery enforces at query time. You attach a data policy to a policy tag in Data Catalog, and any column tagged with it is masked, hashed, or nulled out for callers who lack the unmask role. The API exposes create, list, patch, rename, and delete operations on data policies plus IAM policy management on each resource. Together with policy tags, this lets data platform teams enforce GDPR/HIPAA-style column controls without writing per-query views.

9 endpoints

Binary Authorization API

Binary Authorization is Google Cloud's deploy-time policy engine for container images on GKE, Anthos Service Mesh, Anthos Clusters, and Cloud Run. The API manages policies that require images to be signed by trusted attestors before they can be deployed, plus the attestor resources themselves and their PKIX or PGP keys. It also exposes evaluate to test a policy against an image and validateAttestationOccurrence to verify a signature. Together these endpoints let platform teams enforce supply-chain controls without wedging custom admission webhooks into every cluster.

12 endpoints

Certificate Authority API

The Google Cloud Certificate Authority Service API lets you provision, manage, and operate private certificate authorities (CAs) at scale on Google Cloud. It supports CA pools, root and subordinate CAs, certificate templates, issuance policies, and lifecycle operations such as activate, disable, enable, and revoke. The API also exposes certificate revocation lists, audit-friendly resource hierarchies, and IAM-based access control so private PKI can be automated alongside other Google Cloud workloads.

25 endpoints

Certificate Manager API

Google Cloud Certificate Manager API provisions, stores, and deploys TLS certificates and private trust configurations across Google Cloud load balancers and edge services. It supports Google-managed and self-managed certificates, certificate maps that route SNI-based hostnames to specific certificates, certificate issuance configurations for Certificate Authority Service, and trust configs that pin private CAs. Operations teams use it to automate certificate lifecycle and avoid manual rotation across global load balancer fleets.

18 endpoints

Checks API

Google Checks is a privacy and AI safety compliance platform that scans mobile apps and AI-generated content for policy and regulatory issues, and the Checks API exposes its scan, report, and AI safety classification capabilities programmatically. It supports app privacy reports for Android and iOS bundles, repository scans, AI content classification against safety policies, and management of long-running operations. Product and security teams use it to add automated compliance gates to release pipelines.

11 endpoints

Chrome Policy API

The Chrome Policy API lets Workspace administrators read, modify, and orchestrate Chrome and ChromeOS policies across organisational units, groups, and printers programmatically. It supports batch policy modification, group priority ordering for conflicting policies, network and certificate definitions for managed Wi-Fi, and resolution queries that return the effective policy for a given org unit. It is the write counterpart to the Chrome Management API.

14 endpoints

Cloud IDS API

The Cloud IDS API manages Cloud Intrusion Detection System endpoints on Google Cloud. Cloud IDS is built on Palo Alto Networks threat detection technology and inspects mirrored VPC traffic for malware, spyware, command-and-control activity, and other network-based threats. The API provides CRUD over IDS endpoints attached to a VPC and a region, lists locations where Cloud IDS is available, and exposes long-running operations that track endpoint provisioning. Detected threats themselves are streamed to Cloud Logging and Security Command Center; this API is the control plane for the inspection endpoints, not the threat feed.

8 endpoints

Cloud Key Management Service (KMS) API

Google Cloud KMS is the managed service for cryptographic keys and operations on Google Cloud. The API exposes key rings, crypto keys, key versions, import jobs, and EKM connections, along with cryptographic operations such as encrypt, decrypt, asymmetric sign, asymmetric decrypt, and MAC sign and verify. Agents can rotate keys, restore destroyed key versions within the destruction window, generate cryptographically random bytes, and retrieve a key version's public key for asymmetric verification.

34 endpoints

Container Analysis API

Google Container Analysis API stores and serves vulnerability, build, deployment, and SBOM metadata produced by Artifact Registry scanning, Advanced Vulnerability Insights, and other producers. It exposes notes (the metadata definitions, e.g. a CVE) and occurrences (instances of those notes against a specific resource URL such as a container image). Consumers can list occurrences for an image, attach custom notes, manage IAM on notes, and trigger an SBOM export for a scanned artifact. It is the metadata backbone for image-supply-chain security on Google Cloud.

16 endpoints

Firebase App Check API

The Firebase App Check API helps protect backend resources from abuse such as billing fraud and phishing by attesting that traffic originates from your genuine app. It supports multiple attestation providers including App Attest, Play Integrity, DeviceCheck, reCAPTCHA Enterprise, reCAPTCHA v3, and SafetyNet, exchanging provider tokens for short-lived App Check tokens. Use it to enforce app authenticity for Firestore, Realtime Database, Cloud Functions, and other Firebase backends.

27 endpoints

Firebase Rules API

The Firebase Rules API creates and manages the security rules that determine when a Firebase Rules-enabled service such as Cloud Firestore, Realtime Database, or Cloud Storage should permit a request. It exposes operations to manage rulesets (immutable rule documents), releases (named pointers to rulesets), fetch the executable form of a release, and run rule tests against synthetic requests. Use it to deploy and validate security rules from CI rather than the Firebase console.

9 endpoints

Google Play Integrity API

The Google Play Integrity API helps Android apps confirm that they are interacting with a genuine binary on a genuine Google-Play-licensed device, replacing the deprecated SafetyNet Attestation. Two server-side endpoints decode an integrity token produced by the Play Integrity client library into device, app, and account verdicts, and write a device recall record so the app's backend can detect token replay across reinstalls. Backends use the verdicts to gate sensitive actions like payments, sign-in, and unlocking premium features.

2 endpoints

Google Vault API

The Google Vault API provides programmatic retention and eDiscovery for Google Workspace data including Gmail, Drive, Chat, Meet, Voice, and Groups. It lets compliance teams create matters, place legal holds on accounts and organizational units, run searches across a domain, and export the resulting evidence for review. Access requires Vault privileges and matter-level sharing, and every export, hold, and search action is auditable.

32 endpoints

Google Workspace Alert Center API

The Google Workspace Alert Center API exposes alerts about issues affecting a Workspace domain — phishing campaigns, suspicious account activity, malware, account compromise, and policy violations — that Google's security systems flag. It supports listing, retrieving, undeleting, and batch-deleting alerts, attaching analyst feedback, and reading per-alert metadata. It is intended for security teams that want Workspace alerts pulled into their SIEM or SOAR rather than triaged in the Alert Center web UI.

11 endpoints

KMS Inventory API

The KMS Inventory API gives Google Cloud security teams an organization-wide view of Cloud KMS crypto keys and the resources protected by them. It exposes operations to list every crypto key inside a project, summarize the resources protected by a specific key, and search across an entire organization for resources covered by customer-managed encryption. The API is read-only and complements the standard Cloud KMS API by providing inventory and audit data.

3 endpoints

Network Security API

The Network Security API configures and manages Google Cloud network security policies — address groups, authorization policies, server and client TLS policies, gateway security policies, and security profile groups. It provides the control plane for shaping which traffic is allowed across VPC networks, load balancers, and Google Cloud workloads. Use it to define IP allow lists, enforce mTLS, attach URL filtering rules, and bind security profiles to gateways. The spec exposes 47 endpoints across regional locations and long-running operations.

47 endpoints

On-Demand Scanning API

The On-Demand Scanning API scans container images for OS package and language ecosystem vulnerabilities outside the standard Artifact Registry auto-scan path. It exposes an analyzePackages operation that submits an image (typically resolved by digest) for scanning, then returns a long-running operation whose result lists vulnerability occurrences and their severity. Use it from CI pipelines, ad-hoc security checks, or air-gapped environments where you want explicit control over when an image is scanned. The spec exposes 7 endpoints.

7 endpoints

Organization Policy API

The Organization Policy API configures governance constraints across the Google Cloud resource hierarchy — organisations, folders, and projects. It exposes built-in constraints (boolean, list, custom) and lets administrators author and apply policies that allow or deny specific resource configurations, such as restricting which regions VMs can run in or which service accounts can be created. The API also supports custom constraints for resource fields not covered by built-ins. The spec exposes 9 endpoints.

9 endpoints

Policy Analyzer API

The Google Cloud Policy Analyzer API surfaces activity data that helps organisations understand and right-size their Cloud IAM policies. The single endpoint runs an activities query under a parent organisation, folder, or project, returning records about how IAM permissions and service-account keys have actually been used over a configurable lookback window. Security and compliance teams use that activity data to find unused permissions, dormant service accounts, and over-broad role grants worth removing.

1 endpoints

Policy Simulator API

The Google Cloud Policy Simulator API lets administrators model the impact of a proposed IAM policy change before they apply it. Three endpoints support replay workflows: create a Replay under a parent organisation, folder, or project, fetch a single Replay's status and metadata, and list ReplayResults that show how each historical access request would have been decided under the candidate policy. Security and platform teams use simulations to confirm that tightening a role or removing a binding will not break production access.

3 endpoints

Policy Troubleshooter API

The Google Cloud Policy Troubleshooter API explains why a particular Google Cloud principal would be allowed or denied a specific permission on a specific resource. Its single iam:troubleshoot endpoint accepts an AccessTuple of {principal, fullResourceName, permission} and returns the granted access and an explanation that walks through every IAM policy and binding involved in the decision. Platform and security teams use it to debug surprising access-denied errors and to verify least-privilege role design before rollout.

1 endpoints

Public Certificate Authority API

The Google Public Certificate Authority API creates and manages ACME External Account Binding (EAB) keys associated with Google Trust Services, the publicly trusted CA operated by Google. EAB keys let an ACME client tie its account to a specific Google Cloud project so it can request publicly trusted TLS certificates from Google Trust Services through any RFC 8555 ACME workflow. The API surface is intentionally minimal — its single endpoint mints the EAB key material that downstream ACME clients consume.

1 endpoints

reCAPTCHA Enterprise API

Google reCAPTCHA Enterprise protects websites and apps from fraudulent activity, spam, and abuse using risk scores derived from billions of signals. The API exposes operations to create site keys, evaluate user actions through assessments, define and reorder firewall policies, manage IP overrides, and migrate legacy reCAPTCHA keys. Risk scores returned by assessments power downstream decisions such as showing additional verification, throttling traffic, or blocking outright.

18 endpoints

Safe Browsing API

The Google Safe Browsing API v5 lets client applications check whether URLs and other web resources match Google-curated lists of malware, phishing, and other unsafe content. The v5 surface focuses on a hash-prefix search endpoint that preserves user privacy by sending only a hash prefix to the server. Safe Browsing is licensed for non-commercial use; Web Risk is the commercial equivalent for products that sell or generate revenue from the threat data.

1 endpoints

Secret Manager API

Google Cloud Secret Manager stores sensitive data such as API keys, passwords, certificates, and database credentials with versioning, IAM-based access control, and CMEK encryption. The API lets agents create secrets, add new versions, access specific versions, enable, disable, and destroy versions, and manage replication policies across regions. It is a managed alternative to rolling your own secret store on top of GCS or running HashiCorp Vault.

15 endpoints

Security Command Center API

Security Command Center (SCC) is Google Cloud's centralized vulnerability and threat reporting service for GCP organizations. The API gives programmatic access to assets, findings, sources, and notification configs — the same data surfaced in the SCC dashboard. Agents can list and filter findings, mute or change finding state, group assets and findings, manage notification configs that stream events to Pub/Sub, and run BigQuery exports.

34 endpoints

Sensitive Data Protection (DLP)

Google Sensitive Data Protection (formerly Cloud DLP) is a fully managed service for discovering, classifying, and de-identifying sensitive data such as PII, PHI, and credentials inside text, images, and structured stores. The API supports built-in and custom infoTypes, inspection jobs, deidentify and reidentify operations, hybrid inspection from agents, and continuous data profiling across BigQuery and Cloud Storage. Teams use it for compliance (GDPR, HIPAA), tokenisation, and pre-prompt sanitisation of LLM inputs.

32 endpoints

Web Risk API

The Google Web Risk API lets client applications check URLs against Google's continuously updated lists of unsafe web resources, including phishing pages, malware sites, and unwanted software. It exposes both a hash-based lookup that preserves user privacy and a direct URI search for low-volume use, alongside an evaluate endpoint that returns risk scores for borderline URLs. Web Risk is a paid commercial successor to the public Safe Browsing API and is intended for products that need higher quotas, an SLA, and the ability to submit URLs for review.

8 endpoints

Web Security Scanner API

The Google Web Security Scanner API automates dynamic application security testing for web apps running on App Engine, Compute Engine, and Google Kubernetes Engine. It crawls a target site, executes attack vectors against discovered URLs, and reports vulnerability findings such as cross-site scripting, mixed content, outdated libraries, and insecure cookies. Scans are configured as scanConfigs, executed as scanRuns, and produce findings and crawled-URL artefacts that can be retrieved for triage in CI or security dashboards.

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