How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Google Cloud Dataproc Clusters API

Operations on Dataproc clusters

Google Cloud Dataproc Clusters API is one of 3 APIs that Google Cloud Dataproc publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Cluster. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, a getting-started guide, and 1 JSON Schema.

This API exposes 5 operations across 2 paths, and defines 6 schemas. It is described by OpenAPI 3.1.0, at version v1.

Requests are made against a single base URL, https://dataproc.googleapis.com/v1.

5 operations 2 paths 6 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
v1
Base URL
https://dataproc.googleapis.com/v1
Authentication
OAuth 2.0
License
Resource Areas
1

Authentication & Security 1

Google Cloud Dataproc Clusters API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 1 scope.

Paths & Operations 5

Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Clusters 5

Operations on Dataproc clusters

GET
/projects/{project}/regions/{region}/clusters
Google Cloud Dataproc List clusters
listClusters 5 params → 200
POST
/projects/{project}/regions/{region}/clusters
Google Cloud Dataproc Create a cluster
createCluster 2 params body → 200
GET
/projects/{project}/regions/{region}/clusters/{cluster}
Google Cloud Dataproc Get a cluster
getCluster 3 params → 200
PATCH
/projects/{project}/regions/{region}/clusters/{cluster}
Google Cloud Dataproc Update a cluster
updateCluster 4 params body → 200
DELETE
/projects/{project}/regions/{region}/clusters/{cluster}
Google Cloud Dataproc Delete a cluster
deleteCluster 3 params → 200

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are ClusterConfig (8 properties), Cluster (7 properties), InstanceGroupConfig (5 properties), Operation (5 properties). Each schema is shown below with its type and property counts.

ListClustersResponse
object
2 properties
Cluster
object
7 properties
Operation
object
5 properties
ClusterStatus
object
3 properties
ClusterConfig
object
8 properties
InstanceGroupConfig
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

google-cloud-dataproc-clusters-api-openapi.yml Raw ↑

Other APIs Google Cloud Dataproc publishes across the network.

Google Cloud Dataproc Jobs API
Google Cloud Dataproc WorkflowTemplates API
Where this information came from

This is an independent, third-party profile of Google Cloud Dataproc Clusters API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.