Google Contact Center AI Platform (CCAI Platform) API lets administrators provision and manage tenant-level contact centre instances on Google Cloud. It exposes a small surface for creating contactCenter resources, listing them per project and location, querying validation state, and tracking long-running provisioning operations. CCAI Platform itself bundles cloud telephony, agent desktop, IVR, routing, and reporting; this API handles the platform-level lifecycle. It is currently published as v1alpha1.
9 endpointsThe Firebase Cloud Messaging (FCM) HTTP v1 API delivers push notifications and data messages to Android, iOS, and web clients from a single endpoint. A message can target a specific device registration token, a topic that devices have subscribed to, or a condition combining topics, with platform-specific overrides for Android, APNs, and Web Push payloads. The v1 API replaces the legacy server-key-authenticated /fcm/send endpoint with OAuth 2.0 service account authentication, and it is the canonical interface for transactional and broadcast push messaging on Firebase.
1 endpointsSend, receive, and organize email programmatically through Gmail mailboxes with support for threads, labels, drafts, and push notifications. Access 1.8 billion Gmail accounts' messaging infrastructure including attachment handling, search filtering, and real-time change notifications via pub/sub watches. Supports batch operations for bulk message management and granular OAuth scopes for least-privilege access control.
79 endpointsThe Google Chat API lets applications and bots create and manage spaces, post and update messages, react to user actions, and integrate Chat into automation workflows alongside the rest of Google Workspace. It supports both bot accounts (Chat apps) and user-impersonating OAuth flows, exposing membership management, attachments, message threading, and rich card-based messages. Common uses include incident response bots, deploy notifications, on-call paging, and AI assistants embedded in team conversations.
19 endpointsThe Google Groups Migration API lets Workspace domain administrators import historical email messages, in RFC 822 format, directly into the archive of a Google Group. It is designed for one-way migrations from legacy mailing-list systems (Listserv, Mailman, on-premises archives) into Workspace so that group members can search and reference old discussions in Groups. The API accepts a single endpoint that uploads one message at a time as multipart media, preserving original headers and timestamps. It does not move attachments stored outside the message, send mail, or create groups.
1 endpointsThe My Business Notifications API configures Pub/Sub-based notification settings for Google Business Profile accounts. It exposes a single notificationSetting resource per account that controls which Business Profile events (new reviews, questions, status changes) are pushed to a Cloud Pub/Sub topic. Pair it with the Q&A and v4 reviews endpoints to build event-driven Business Profile workflows instead of polling.
2 endpointsStep 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 | shStep 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 instanceJentic 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.