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.

Can I limit what my agent is allowed to do with the Google Cloud Support API?

Yes. Jentic One is self-hosted, so your own rules decide which Cloud Support operations and OAuth credentials the agent may use. Because each case resource name sits in the URL path (for example /v2/{+name}:close and /v2/{+parent}/attachments), you can pin the agent to a single case so it only lists and downloads that case's attachments and nothing else. You pick the operations it may call, so write actions like closing or escalating a case are excluded unless you explicitly add them.