Google APIs

274 APIs7,055 Endpoints22 Categories

API Catalog(20 of 274)

Admin SDK API

The Admin SDK API gives Google Workspace administrators programmatic control over their domains. The Directory surface manages users, groups, group members, organisational units, role assignments, mobile devices, ChromeOS devices, building and resource calendars, and domain aliases. Companion surfaces (Reports and Data Transfer) provide audit and usage reports and orchestrate user-data hand-offs during offboarding. Workspace ops teams use it to automate joiner-mover-leaver workflows, enforce device policies, and feed identity data into downstream HR and security tooling.

123 endpoints

Android Device Provisioning Partner API

The Android Device Provisioning Partner API automates Android zero-touch enrollment for device resellers, enterprise customers, and EMM providers. Resellers use it to claim devices for customers so they can self-deploy, and customers can list, configure, and unclaim corporate-owned Android devices at scale. The API supports synchronous and asynchronous device claim operations, configuration management, and customer linkage so that thousands of devices can be staged before they are unboxed.

24 endpoints

Android Management API

The Android Management API provides remote enterprise management of Android devices and apps. Administrators define policies, enroll devices via enrollment tokens, push apps from managed Google Play, and issue commands such as lock, reboot, and wipe. The API also exposes web apps, web tokens for managed Play iframes, and operation handles for long-running device commands.

18 endpoints

BeyondCorp API

The BeyondCorp API manages Google Cloud's zero-trust access product, exposing operations to provision and manage app connectors, app gateways, and the application links that connect users to internal applications without a VPN. App connectors report their status and resolve their instance configuration via dedicated endpoints, and the API supports long-running operations for create, patch, and delete flows. The API is the control plane that wires identity-aware proxies into enterprise applications. It does not authenticate end users or evaluate access policies at request time.

23 endpoints

Chrome Verified Access API

The Chrome Verified Access API lets enterprise services confirm that a request originates from a managed, policy-compliant Chrome device or ChromeOS user before granting access to sensitive resources. The integration uses a challenge-response handshake: the relying server requests a challenge, the Chrome client signs it via the Verified Access extension, and the server verifies the signed response against Google. It is used for zero-trust gating of internal apps, VPNs, and SaaS resources.

2 endpoints

Cloud Identity API

Google Cloud Identity is the directory service that backs Google Workspace and standalone Cloud Identity tenancies. The API provisions and manages users, groups, group memberships, devices, inbound SAML SSO profiles, and policies. Agents can create groups, search the directory, lookup group keys, manage device enrollment, and configure inbound SSO assignments that delegate authentication to an external identity provider. It is the surface to use when an organisation needs to script directory operations rather than going through the Admin Console.

36 endpoints

Cloud Identity-Aware Proxy API

The Cloud Identity-Aware Proxy (IAP) API manages the configuration that fronts internal applications on Google Cloud with identity- and context-based access control. It is used to register OAuth brands and clients, configure per-resource IAP settings (such as access expressions and IAP-TCP tunnel options), maintain destination groups for TCP forwarding, validate attribute expressions, and reset OAuth client secrets. IAP itself enforces access at the load balancer in front of HTTP backends and Compute Engine VMs; this API is the control plane that defines how that enforcement behaves.

16 endpoints

Cloud OS Login API

The Cloud OS Login API manages SSH access to Google Compute Engine VMs through IAM identities rather than per-VM key files. It exposes the user's login profile (POSIX username, UID/GID, secondary aliases) and lets administrators import, delete, and update SSH public keys associated with that identity. Use it to centralise SSH access management, remove a former employee's keys across all VMs at once, or build automation that issues short-lived SSH keys to engineers. The spec exposes 6 endpoints.

6 endpoints

Data Portability API

The Google Data Portability API lets a third-party application request authorization from a Google user to copy their data out of Google services into the application. It exposes 6 endpoints that initiate a portability archive, check whether the granted authorization is one-time or time-based, retry partial archives, and reset the granted authorization. The API is the programmatic surface behind Google Takeout-style data exports for product integrations.

6 endpoints

Digital Asset Links API

Google Digital Asset Links lets web and mobile owners declare verifiable relationships between online assets — for example, that an Android app is the official companion to a website. Apps and platforms use the API to check whether a given source asset (a website) has authorized a target asset (an Android app) for actions like Smart Lock for Passwords, App Links, and Chrome Custom Tabs verification. The lookups are unauthenticated GETs over public statement files (assetlinks.json) hosted on the source asset.

3 endpoints

Enterprise License Manager API

The Enterprise License Manager API lets Google Workspace administrators assign, change, and revoke product licenses for users in a customer they manage. It exposes operations to insert a license assignment, get or update an assignment, list assignments by product or by product and SKU, and delete an assignment. The API is the programmatic equivalent of the Apps Admin licensing console and is essential for automating onboarding, role changes, and offboarding at scale.

7 endpoints

Google Identity Toolkit API

The Google Identity Toolkit API v3 is the relying-party endpoint set used by Firebase Authentication and the legacy Identity Toolkit product to manage user accounts and federated sign-in. It exposes operations for creating, retrieving, updating, and deleting accounts, sending email verification and password-reset codes, exchanging credentials for ID tokens, signing users up and in with email and password, and uploading or downloading bulk account data. Newer Firebase Auth deployments use the Identity Toolkit v2 surface; v3 remains the system of record for many existing apps and toolchains.

20 endpoints

Google OAuth2 API

The Google OAuth2 API surfaces the lightweight identity endpoints that complement the broader Google OAuth 2.0 token flow — the userinfo endpoint that returns profile claims for an authenticated user, and the tokeninfo endpoint that introspects a Google-issued access or ID token. Use it after a sign-in flow to retrieve a user's basic profile (email, name, picture, locale) or to validate that a token is still active and was issued for the expected client. The spec exposes 3 endpoints.

3 endpoints

Google Site Verification API

The Google Site Verification API lets owners prove control over a website or DNS domain so that Google services like Search Console, Analytics, AdSense, and Webmaster Tools recognise them as the verified owner. Agents request a verification token (HTML file, meta tag, DNS TXT, or DNS CNAME), place it on the property, and then call insert to verify ownership. Verified resources can be listed, retrieved, updated, and deleted, and ownership can be shared with other Google accounts.

7 endpoints

IAM Service Account Credentials API

The IAM Service Account Credentials API mints short-lived credentials for Google Cloud service accounts. A caller with iam.serviceAccountTokenCreator on a target service account can request a 1-hour OAuth 2.0 access token, an OpenID Connect ID token, a signed JWT, or a signed binary blob, all issued in the target service account's identity. This is the standard mechanism for service-account impersonation, workload identity federation, and key-less signing on Google Cloud, replacing the practice of distributing long-lived service-account JSON keys.

5 endpoints

Identity and Access Management (IAM) API

The Identity and Access Management (IAM) API v2 manages deny policies that supplement Google Cloud's allow-based IAM bindings. A deny policy is attached to an organisation, folder, or project resource and lists permissions that must not be granted regardless of any allow rule. The v2 API provides CRUD over these deny policies and supports long-running operation tracking for asynchronous policy updates. It is the modern surface for fine-grained, exception-based access control on Google Cloud and is paired with the broader IAM v1 surface for service accounts, allow policies, and roles.

5 endpoints

Managed Service for Microsoft Active Directory API

Managed Service for Microsoft Active Directory provides a hardened, highly available Microsoft AD running on Google Cloud, with the API covering domain provisioning, trust relationships, schema extension, LDAPS configuration, backups, and migration from existing on-premises forests. Operations are scoped to project locations and most state changes return long-running operation handles for polling. The API also exposes domain-join helpers, peerings, and SQL integration controls used by hybrid Windows workloads.

28 endpoints

My Business Account Management API

The My Business Account Management API manages access and ownership for Google Business Profile accounts and locations. It exposes accounts, admins, and invitations resources so organisations can programmatically grant or revoke management rights, transfer locations between accounts, and respond to incoming admin invitations. It is the access-control layer of the Business Profile API family — pair it with the Business Information, Q&A, and verifications APIs to manage the actual listing content.

11 endpoints

My Business Verifications API

The My Business Verifications API runs the ownership verification flow for Google Business Profile locations. It exposes endpoints to fetch the verification options available to a location (postcard, phone, email, video), start a verification, complete it with a code, list past attempts, and read the Voice of Merchant state that gates listing visibility. Pair it with the Business Information API after verification succeeds to start managing listing content.

5 endpoints

Security Token Service API

Google Security Token Service exchanges Google or third-party credentials for short-lived OAuth 2.0 access tokens scoped to specific Google Cloud resources. It underpins workload identity federation, letting workloads running on AWS, Azure, OIDC providers, or SAML-based identity systems impersonate Google service accounts without long-lived service-account keys. The single endpoint accepts a subject token plus a target scope and returns a federated access token suitable for calling any Google Cloud API.

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