Google APIs

274 APIs7,055 Endpoints22 Categories

API Catalog(3 of 274)

Google Cloud Support API

The Google Cloud Support API manages technical support cases for the Customer Care offerings attached to a GCP organization, project, or billing account. It exposes case creation, search, escalation, comment threads, and attachment download so support teams can integrate Google's support workflow into their own ticketing and incident systems. It is most often used to mirror cases into ServiceNow or Jira, automatically escalate critical issues, and pull case histories into postmortems.

13 endpoints

My Business Q&A API

The My Business Q&A API manages questions and answers that appear on Google Business Profile listings in Search and Maps. It exposes questions and answers resources per location, with create, list, update, delete, and upsert flows so businesses can post owner-authored questions, reply to customer questions, and curate answer threads. Combine with the Notifications API for real-time question alerts and the Business Information API to keep the parent listing accurate.

7 endpoints

People API

The Google People API provides programmatic access to a user's profile and contacts stored in their Google Account. Applications can read and write personal contacts, organise them into contact groups, and access read-only profile data and other-contacts inferred from email and chat interactions. The API supports batched lookups and structured field masks so callers fetch only the fields they need across 23 endpoints covering people, contactGroups, and otherContacts resources.

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