Cloud Storage JSON API

Name: Cloud Storage JSON API API
Brand: Cloud Storage JSON API
Availability: InStock

✓ Official Vendor SpecStorageObject Storageoauth281 EndpointsREST

For Agents

Upload, download, copy, and manage objects in Google Cloud Storage buckets. Configure bucket lifecycle, IAM, retention, and Pub/Sub notifications.

Quickstart

Get started with Cloud Storage JSON 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:
"upload a file to Cloud Storage"

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

Capabilities

What an agent can do with Cloud Storage JSON API API.

Create, list, update, and delete Cloud Storage buckets with chosen storage class and location

Upload, download, copy, compose, and rewrite objects within and across buckets

Manage bucket and object ACLs and IAM policies at fine granularity

Configure lifecycle rules, retention policies, and object versioning on a bucket

GET STARTED

Start building with Cloud Storage JSON API API

Explore with Jentic

View OpenAPI Document

The Cloud Storage JSON API manages buckets and objects on Google Cloud Storage. It covers bucket lifecycle and configuration (location, storage class, retention policy, CORS, lifecycle rules, IAM), object operations (insert, get, list, copy, compose, rewrite, delete), ACL management at both bucket and object level, HMAC keys for interoperable access, notifications to Pub/Sub, and Anywhere Cache resources for low-latency regional reads. Object content uploads use the dedicated upload host with multipart or resumable protocols.

Use Cases

Patterns agents use Cloud Storage JSON API API for, with concrete tasks.

★ Static Asset Hosting

Host product images, JavaScript bundles, and static HTML in a public Cloud Storage bucket fronted by a CDN. The Storage JSON API exposes bucket creation with website settings, object insert with cache-control metadata, and IAM policy management to make objects publicly readable. Lifecycle rules can transition cold assets to cheaper storage classes automatically.

POST /b with name=static.example.com, location=US, then upload index.html via the upload host with cacheControl='public, max-age=300'.

Lakehouse Ingestion

Ingest source files into a Cloud Storage data lake by uploading partitioned objects under date-prefixed paths, then publish a Pub/Sub notification on each new object so downstream pipelines pick them up. The API supports object insert, list-with-prefix for catalog scans, and notifications for change events.

Upload events_2026-06-10.parquet under bucket 'events-raw' with prefix 'date=2026-06-10/', then POST /b/events-raw/notificationConfigs with topic=projects/p/topics/raw-events.

Compliance Retention

Apply a bucket-level retention policy that locks objects against deletion for the regulatory retention window. The Storage JSON API exposes retentionPolicy with both a soft retention period and a lock action that makes the policy permanent for compliance officers' sign-off.

PATCH /b/audit-logs with retentionPolicy.retentionPeriod=2592000 (30d), then POST /b/audit-logs/lockRetentionPolicy.

AI Agent Document Workflow

An AI agent processing a user's uploaded contracts uploads each document to a Cloud Storage bucket, then triggers downstream extraction. Through Jentic, the agent searches for the upload operation, loads the schema, and executes — Jentic handles auth so the agent never sees the underlying access token.

Search Jentic for 'upload a file to Cloud Storage', execute the object insert call against bucket 'contracts' with the file content and contentType='application/pdf'.

Key Endpoints

81 endpoints — the cloud storage json api manages buckets and objects on google cloud storage.

METHOD

PATH

DESCRIPTION

GET

List buckets in a project

POST

Create a new bucket

GET

/b/{bucket}

Get a bucket's metadata

GET

/b/{bucket}/acl

List the ACL entries on a bucket

GET

/b/{bucket}/folders

List folders in a hierarchical-namespace bucket

GET

/b/{bucket}/anywhereCaches

List Anywhere Cache resources on a bucket

POST

/b/{bucket}/anywhereCaches/{anywhereCacheId}/pause

Pause an Anywhere Cache resource

GET

List buckets in a project

POST

Create a new bucket

GET

/b/{bucket}

Get a bucket's metadata

GET

/b/{bucket}/acl

List the ACL entries on a bucket

GET

/b/{bucket}/folders

List folders in a hierarchical-namespace bucket

GET

Why though Jentic?

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

Credential isolation

Cloud Storage OAuth credentials and HMAC keys are stored in the Jentic vault (MAXsystem) and exchanged for scoped, short-lived access tokens on each call. Long-lived service-account JSON keys never enter the agent context.

Intent-based discovery

Agents search Jentic with intents like 'upload a file to Cloud Storage' or 'list objects in a bucket', and Jentic returns the matching objects.insert or objects.list operation along with its request schema.

Time to first call

Direct Cloud Storage integration: 1-2 days to wire OAuth, resumable upload protocol, and lifecycle/IAM management. Through Jentic: under 1 hour for the common upload, list, and copy operations.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Backblaze B2

Backblaze B2 is a low-cost S3-compatible object storage service.

Choose Backblaze B2 when storage cost is the top priority and S3-compatible APIs are sufficient. Choose Cloud Storage when integration with BigQuery, Dataflow, and Google IAM matters.

Complementary

Storage Transfer API

Storage Transfer schedules bulk migrations of data into Cloud Storage from S3, on-premises, or another bucket.

Use Storage Transfer when moving large volumes of data into Cloud Storage on a schedule. Use the Storage JSON API for individual object operations.

Complementary

Cloud Pub/Sub API

Pub/Sub topics receive object change notifications published by Cloud Storage buckets.

Use Pub/Sub when wiring downstream pipelines that should react to object create, update, or delete events on a bucket.

Alternative

Dropbox API

Dropbox is consumer- and team-oriented file storage rather than infrastructure object storage.

Choose Dropbox for end-user file collaboration. Choose Cloud Storage for backend infrastructure objects, data lakes, and CDN-fronted assets.

FAQs

Specific to using Cloud Storage JSON API API through Jentic.

What authentication does the Cloud Storage JSON API use?

The Cloud Storage JSON API uses OAuth 2.0 with scopes such as devstorage.read_only, devstorage.read_write, or cloud-platform. HMAC keys are also supported for S3-compatible interoperability. Through Jentic, OAuth credentials are stored in the Jentic vault (MAXsystem) and exchanged for short-lived access tokens.

Can I upload large files with the Storage JSON API?

Yes. Object uploads use the upload host (uploadType=resumable for files over a few MiB), which supports chunked, resumable transfers. The metadata-only POST /b/{bucket}/o initiates the resumable session and returns an upload URL the client streams content into.

What are the rate limits for the Cloud Storage JSON API?

Cloud Storage scales to very high object operation rates per bucket but enforces a soft limit of around 1 write per second per object name and recommended ramp-up patterns for new buckets. Per-project read and write quotas exist and can be inspected in the Google Cloud Console under IAM and admin > Quotas.

How do I copy an object between buckets through Jentic?

Search Jentic for 'copy a Cloud Storage object', load the objects.copy or objects.rewrite schema, and execute. POST /b/{sourceBucket}/o/{sourceObject}/copyTo/b/{destBucket}/o/{destObject} performs the copy in a single call; objects.rewrite is used for cross-region copies and storage class transitions on large objects.

Is the Cloud Storage JSON API free?

The API itself has no per-call charge. Cloud Storage costs come from storage volume per GB-month, network egress, and operation classes (Class A for writes, Class B for reads). A free tier of 5 GB Standard storage and limited operations is available.

Can I receive notifications when an object changes?

Yes. POST /b/{bucket}/notificationConfigs registers a Pub/Sub topic that receives object lifecycle events such as OBJECT_FINALIZE and OBJECT_DELETE, which downstream pipelines can subscribe to.