Cloud SQL Admin API

Name: Cloud SQL Admin API API
Brand: Cloud SQL Admin API
Availability: InStock

✓ Official Vendor SpecStorageDatabaseoauth268 EndpointsREST

For Agents

Provision and operate managed MySQL, PostgreSQL, and SQL Server instances on Google Cloud. Run backups, manage databases and users, and orchestrate import/export through the legacy /sql/v1beta4 path.

Quickstart

Get started with Cloud SQL Admin 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:
"create a Cloud SQL instance"

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

Capabilities

What an agent can do with Cloud SQL Admin API API.

Create, list, update, and delete managed Cloud SQL instances across MySQL, PostgreSQL, and SQL Server

Take on-demand backups and list scheduled backup runs for an instance

Manage databases, users, and SSL certificates on each instance

Run import and export jobs that move data between Cloud SQL and Cloud Storage

GET STARTED

Start building with Cloud SQL Admin API API

Explore with Jentic

View OpenAPI Document

The Cloud SQL Admin API (v1beta4) administers managed MySQL, PostgreSQL, and SQL Server instances on Google Cloud. It covers instance lifecycle (create, clone, restart, restore from backup, failover, switchover), database and user management, scheduled and on-demand backups, server certificates, IP configuration, and import/export jobs to and from Cloud Storage. The v1beta4 surface is the longstanding stable beta path; new automation should generally prefer the v1 path, but v1beta4 remains supported for existing tooling.

Use Cases

Patterns agents use Cloud SQL Admin API API for, with concrete tasks.

★ Managed MySQL Provisioning

Provision a new MySQL instance with a chosen tier, region, and backup window for a service team. The Cloud SQL Admin API exposes instance creation and update as long-running operations under /sql/v1beta4/projects/{project}/instances. Combined with calls to create the initial database and a service user, the full setup takes a few minutes.

POST /sql/v1beta4/projects/myproj/instances with databaseVersion=MYSQL_8_0, settings.tier=db-custom-2-7680, settings.backupConfiguration.enabled=true.

Scheduled Logical Backups to Cloud Storage

Run nightly logical exports of a production Cloud SQL database to a Cloud Storage bucket for offsite retention. The export endpoint accepts the bucket URI, database list, and SQL or CSV format. Each export is a long-running operation that can be polled until done.

POST /sql/v1beta4/projects/myproj/instances/prod/export with exportContext.uri=gs://backups/prod-2026-06-10.sql.gz and databases=['app_db'].

Disaster Recovery Drill

Exercise the recovery runbook by restoring a recent backup into a fresh instance and verifying application connectivity. The Cloud SQL Admin API supports restoreBackup against an existing instance and clone for creating a separate instance from a point-in-time. Both are long-running operations.

POST /sql/v1beta4/projects/myproj/instances/prod/restoreBackup with backupRunId of last night's run, then verify the operation completes.

AI Agent Database Onboarding

An AI agent setting up a new microservice creates a Cloud SQL instance, then a database and an application-scoped user. Through Jentic, the agent searches for the create operations, loads each schema, and executes them in order — the entire onboarding fits inside a single agent reasoning loop.

Search Jentic for 'create a Cloud SQL instance', execute the create call, then chain databases.insert and users.insert against the new instance.

Key Endpoints

68 endpoints — the cloud sql admin api (v1beta4) administers managed mysql, postgresql, and sql server instances on google cloud.

METHOD

PATH

DESCRIPTION

GET

/sql/v1beta4/projects/{project}/instances

List Cloud SQL instances in a project

GET

/sql/v1beta4/projects/{project}/instances/{instance}

Get a single Cloud SQL instance

POST

/sql/v1beta4/projects/{project}/instances/{instance}/backupRuns

Take an on-demand backup

POST

/sql/v1beta4/projects/{project}/instances/{instance}/clone

Clone an instance, optionally to a point in time

GET

/sql/v1beta4/projects/{project}/instances/{instance}/databases

List databases on an instance

GET

/sql/v1beta4/projects/{project}/instances/{instance}/connectSettings

Read connection settings for an instance

GET

/sql/v1beta4/projects/{project}/instances

List Cloud SQL instances in a project

GET

/sql/v1beta4/projects/{project}/instances/{instance}

Get a single Cloud SQL instance

POST

/sql/v1beta4/projects/{project}/instances/{instance}/backupRuns

Take an on-demand backup

POST

/sql/v1beta4/projects/{project}/instances/{instance}/clone

Clone an instance, optionally to a point in time

GET

/sql/v1beta4/projects/{project}/instances/{instance}/databases

List databases on an instance

Why though Jentic?

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

Credential isolation

Cloud SQL Admin OAuth credentials are stored in the Jentic vault (MAXsystem) and exchanged for scoped, short-lived access tokens. Service-account JSON keys never enter the agent context.

Intent-based discovery

Agents search Jentic with intents like 'create a Cloud SQL instance' or 'export a Cloud SQL database', and Jentic returns the matching instances.insert or instances.export operation along with its v1beta4 request schema.

Time to first call

Direct Cloud SQL Admin integration: 1-2 days to wire OAuth, long-running operation polling, and the instance settings schema. Through Jentic: under 1 hour for discover, schema-load, and execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Cloud SQL Admin API (v1)

Same resource model exposed under the v1 path; preferred for new integrations.

Choose sqladmin (v1) for new automation. Use this v1beta4 surface only when an existing client library or runbook is pinned to /sql/v1beta4.

Alternative

Cloud Spanner API

Spanner is globally distributed strongly consistent SQL; Cloud SQL is a regional managed MySQL/Postgres/SQL Server.

Choose Spanner for global write scale and strong consistency. Choose Cloud SQL when you want managed MySQL, Postgres, or SQL Server semantics in a single region.

Alternative

AlloyDB API

AlloyDB is a higher-performance Postgres-compatible service tuned for analytics-on-OLTP.

Choose AlloyDB when Postgres compatibility and heavier mixed workloads are the priority. Choose Cloud SQL for general-purpose managed MySQL/Postgres/SQL Server.

Complementary

Cloud Storage JSON API

Cloud Storage holds the dump files used by Cloud SQL import and export operations.

Use Cloud Storage to manage the gs:// buckets and lifecycle rules for Cloud SQL exports before invoking the import/export endpoints.

FAQs

Specific to using Cloud SQL Admin API API through Jentic.

What authentication does the Cloud SQL Admin API use?

The Cloud SQL Admin API uses OAuth 2.0 with the cloud-platform or sqlservice.admin scope. Through Jentic, OAuth credentials are stored in the Jentic vault (MAXsystem) and exchanged for short-lived access tokens, so service-account JSON keys never enter the agent context.

Can I take a Cloud SQL backup with this API?

Yes. POST /sql/v1beta4/projects/{project}/instances/{instance}/backupRuns triggers an on-demand backup, and GET on the same path lists existing backup runs. Both calls return the long-running operation handle that tracks the backup until completion.

What is the difference between the v1beta4 and v1 Cloud SQL Admin API surfaces?

v1beta4 was the original stable beta path under /sql/v1beta4 and remains supported for backward compatibility. The v1 path under /v1 (sqladmin) is now generally available with the same resource model. New automation should typically target v1; v1beta4 is exposed here for tooling that already calls /sql/v1beta4.

What are the rate limits for the Cloud SQL Admin API?

Admin API quotas default to a few hundred requests per minute per project, with stricter limits on instance creation and import/export operations. Quotas can be inspected and raised in the Google Cloud Console under IAM and admin > Quotas.

How do I export a database to Cloud Storage through Jentic?

Search Jentic for 'export a Cloud SQL database', load the instances.export schema, and execute POST /sql/v1beta4/projects/{project}/instances/{instance}/export with the destination gs:// URI and target databases. Jentic returns the long-running operation handle for polling.

Is the Cloud SQL Admin API free?

The Admin API itself has no per-call charge. Cloud SQL costs come from the underlying instance compute, storage, and backup retention, billed per hour and per GB.