Google Cloud Support API

Name: Google Cloud Support API
Brand: Google Cloud Support API
Availability: InStock

✓ Official Vendor SpecCRMCustomer Supportoauth213 EndpointsREST

Install Jentic One Beta

Connect the Google Cloud Support API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Google Cloud Support API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

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.

Capabilities

What an agent can do with Google Cloud Support API.

Open Google Cloud support cases under a project, folder, or organization parent

Search cases by priority, product, or update time and read full case details

Add threaded comments to an existing case from an internal ticketing system

GET STARTED

Start building with Google Cloud Support API

Explore with Jentic

View OpenAPI Document

For Agents

Open, comment on, escalate, and close Google Cloud support cases programmatically and download case attachments. Lets agents drive Google's support workflow from inside an internal incident system.

Use for: I need to open a Google Cloud support case, Search for support cases by priority or product, Add a comment to an existing support case, Escalate a Google Cloud support case to a higher tier

Not supported: Does not raise tickets for non-Google products, manage Google Workspace support, or process billing disputes - use for technical Google Cloud support cases under Customer Care offerings only.

Use Cases

Patterns agents use Google Cloud Support API for, with concrete tasks.

★ Mirror Cloud Cases Into ServiceNow

Pipe new and updated Google Cloud support cases into an internal ITSM system so on-call engineers can triage everything from one queue. The API exposes case search and per-case get with comments, letting an integration poll for changes or push updates back to Google with a write-through pattern. Most rollouts are live in under a week.

Search for cases with priority=P1 created in the last 24 hours and create a matching ServiceNow incident for each one

Programmatic Case Escalation

Auto-escalate Google Cloud support cases when an internal SLO is at risk. The escalate endpoint accepts a reason and a justification and pushes the case to the next response tier without a human waiting on hold. Pair it with a watcher that monitors customer impact metrics and you have a hands-off escalation path.

If case projects/acme/cases/123 is older than two hours and has priority=P2, call the escalate endpoint with reason=BUSINESS_IMPACT

Postmortem Evidence Collection

Pull the full transcript and attachments of a Google Cloud support case into a postmortem document. The API exposes attachments.list and a download endpoint so an agent or runbook can fetch logs and screenshots Google's support engineers shared, attach them to an incident report, and close the case once everything is captured.

List attachments on case projects/acme/cases/789, download each via the download endpoint, and attach them to the matching incident doc

Agent-Mediated Case Filing

An AI agent embedded in a developer tool can file a Google Cloud support case on behalf of the user when an error matches a known unsupported scenario. Through Jentic the agent searches for 'create google cloud support case', loads the cases.create schema, and submits the case with the right classification without the user leaving the tool.

Use Jentic to call cases.create under projects/acme with display_name='BigQuery slot exhaustion', priority=P2, and the matching case classification

Key Endpoints

13 endpoints — the google cloud support api manages technical support cases for the customer care offerings attached to a gcp organization, project, or billing account.

METHOD

PATH

DESCRIPTION

GET

/v2/caseClassifications:search

Look up valid case classifications before filing

POST

/v2/{+name}:close

Close a resolved support case

POST

/v2/{+name}:escalate

Escalate a case to a higher response tier

GET

/v2/{+name}:download

Download an attachment from a case

GET

/v2/{+parent}/attachments

List attachments on a case

GET

/v2/caseClassifications:search

Look up valid case classifications before filing

POST

/v2/{+name}:close

Close a resolved support case

POST

/v2/{+name}:escalate

Escalate a case to a higher response tier

GET

/v2/{+name}:download

Download an attachment from a case

GET

/v2/{+parent}/attachments

List attachments on a case

Why Jentic?

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

Credential isolation

Your Cloud Support OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a Google Cloud support case' or 'escalate a support case', and Jentic returns the matching Cloud Support operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Google Cloud Support API through Jentic.

What authentication does the Cloud Support API use?

It uses Google OAuth 2.0 with the https://www.googleapis.com/auth/cloud-platform scope. Through Jentic the OAuth credentials are stored encrypted in your Jentic One instance and only short-lived access tokens are sent to the agent runtime.

Can I escalate a support case with the API?

Yes. Call POST on /v2/{name}:escalate with an escalation reason and justification. The case is moved to a higher response tier immediately and the action is recorded in the case timeline.

What are the rate limits for the Cloud Support API?

Google enforces per-organization quotas on case writes such as create, escalate, and close, with read endpoints like search and get allowed at higher rates. Bulk integrations should rely on incremental search with a sort by update_time and avoid retrying writes in tight loops.

How do I create a support case through Jentic?

Search Jentic for 'create google cloud support case', load the cases.create schema, and execute the call against /v2/{parent}/cases with display_name, description, priority, and classification fields. Jentic returns the schema so the agent fills only the required fields.

Does Cloud Support API access require a paid support plan?

Yes. The account or organization must have an active Google Cloud Customer Care offering before cases can be created. The API itself has no per-call price beyond the support plan cost.

Can I download attachments from a support case?

Yes. List the attachments under /v2/{parent}/attachments and call the download endpoint at /v2/{name}:download to stream the file contents. This is useful when collecting Google-supplied logs into an internal postmortem.

Google Cloud Support API

Connect the Google Cloud Support API to your agent

Capabilities

Start building with Google Cloud Support API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs