Google Chat API

Name: Google Chat API API
Brand: Google Chat API
Availability: InStock

✓ Official Vendor SpecCommunicationsChat Messagingoauth219 EndpointsREST

For Agents

Create Google Chat spaces, post and update messages with rich cards, manage memberships, and operate Chat bots and apps inside Google Workspace.

Quickstart

Get started with Google Chat API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"post a message to a Google Chat space"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Google Chat API API.

Create direct messages and named spaces between users and Chat apps

Post text and card-formatted messages to a space, optionally inside a thread

Update or delete messages previously posted by the calling Chat app

Manage memberships by adding, removing, and listing space members

GET STARTED

Start building with Google Chat API API

Explore with Jentic

View OpenAPI Document

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

Use Cases

Patterns agents use Google Chat API API for, with concrete tasks.

★ Incident Response Notifications

DevOps teams wire monitoring tools into a Google Chat app that creates an incident space, posts a structured card with severity and runbook links, and adds the on-call responders as members. The same app can post status updates to the original thread as the incident progresses. Card messages render the same on web and mobile.

Create a space named "INC-1234 — payments-api 5xx spike", add on-call@example.com as a member, and post a card message with severity SEV2 and a runbook link.

Deploy and CI Notifications

Engineering teams post deploy and CI status messages to a #releases space from their pipeline. The Chat app uses a single POST /v1/spaces/{space}/messages call per event and threads follow-up messages under the original deploy message. This replaces email blasts with a single readable timeline per release.

Post a threaded message under deploy parent thread with text "deploy to prod completed: build #482" via /v1/spaces/{space}/messages with messageReplyOption=REPLY_MESSAGE_FALLBACK_TO_NEW_THREAD.

AI Assistant Embedded in a Team Space

An AI assistant joins a project space as a Chat app, listens for slash commands or @mentions, and responds with summaries, action items, or links to ticket creation. The assistant uses spaces.messages to reply and spaces.members to enumerate participants for context. Workspace admin approval is required for the Chat app to publish to other domains.

When a slash command /summarise is received, post a reply in the same thread with a summary of the last 50 messages in the space.

AI Agent Workspace Operator via Jentic

An AI agent through Jentic acts as a project assistant — creating a Chat space for a new initiative, inviting the right teammates by email, posting an onboarding card, and uploading the kickoff doc as an attachment. Jentic isolates the Workspace OAuth credentials and exposes the Chat operations as named tools.

Through Jentic, search chat_create_message, load schema, and execute it for space spaces/AAAA with text "Kickoff at 10am — agenda attached".

Key Endpoints

19 endpoints — the 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.

METHOD

PATH

DESCRIPTION

POST

/v1/spaces

Create a Chat space

GET

/v1/spaces

List spaces a Chat app is a member of

GET

/v1/spaces:findDirectMessage

Find the direct message space between two users

POST

/v1/spaces:setup

Create a space and add members in a single call

PUT

/v1/{+name}

Update a previously posted message

POST

/v1/{+parent}/attachments:upload

Upload an attachment for a Chat message

POST

/v1/spaces

Create a Chat space

GET

/v1/spaces

List spaces a Chat app is a member of

GET

/v1/spaces:findDirectMessage

Find the direct message space between two users

POST

/v1/spaces:setup

Create a space and add members in a single call

PUT

/v1/{+name}

Update a previously posted message

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Google Workspace OAuth credentials and Chat app service accounts are stored encrypted in the Jentic vault (MAXsystem). Agents call Chat with short-lived access tokens — refresh tokens and service account JSON never enter the agent context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'post a Google Chat message') and Jentic returns the spaces.messages.create operation with its parameter schema, including support for cardsV2 layouts.

Time to first call

Direct integration: 1-2 days for OAuth or service account setup, scope review, and Workspace admin approval. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Gmail API

Send and read email instead of posting to a real-time chat space.

Choose Gmail when the audience is asynchronous and external; choose Chat when the audience is internal and expects real-time updates.

Complementary

Google Drive API

Store and share files that can be linked or attached in Chat messages.

Use Drive to upload a document and Chat to share the link in a space.

Complementary

Google Calendar API

Schedule meetings to follow up on a Chat conversation.

Pair with Chat when an agent moves a discussion from text to a scheduled meeting.

FAQs

Specific to using Google Chat API API through Jentic.

What authentication does the Google Chat API use?

It supports two flows: a Chat app service account using OAuth 2.0 with the chat.bot scope, and user-impersonation OAuth with scopes such as chat.spaces and chat.messages. Through Jentic, the chosen credential is stored encrypted in the Jentic vault and the agent receives only short-lived access tokens.

Can I post a message to a Google Chat space via the API?

Yes. POST to /v1/{parent}/messages where parent is the space resource name (spaces/AAAA). The body can include text, cardsV2 for rich card layouts, and threadKey or thread.name to post inside an existing thread.

What are the rate limits for the Google Chat API?

Google Workspace applies per-app per-user write quotas, typically around 60 messages per minute per space for a single Chat app, with higher project-level quotas. Bursts above the per-space rate return 429 and require backoff.

How do I create a Chat space through Jentic?

Use the Jentic search query "create a Google Chat space" to discover the spaces.create operation, load its schema, and execute it with displayName and spaceType (SPACE or DIRECT_MESSAGE). Run pip install jentic to get started.

Can a Chat app update or delete messages?

A Chat app can update and delete only the messages it posted itself. Use PUT /v1/{+name} with an updateMask covering the fields to change, and DELETE /v1/{+name} to remove a message.

Is the Google Chat API free?

The API itself has no per-call charge. It is available to Google Workspace customers; some features (such as enterprise external Chat apps) require specific Workspace editions.