Cloud Runtime Configuration API logo

Cloud Runtime Configuration API

Cloud Runtime Configuration API

Manage runtime configs, variables, waiters, and watch operations for dynamic configuration workflows.

Visit site ↗Health checked 9h ago
Use it when

Provides concrete variable, waiter, and watch paths

Watch for

The exposed API version is v1beta1

First check

Start by listing or creating configs, then validate variables, waiters, and the {name}:watch operation. For change-driven jobs, focus on watch and waiter behavior first.

Auth
oauth
CORS
No
HTTPS
Yes
Signup
Required
Latency
41 ms
Protocol
REST
Pricing

Uptime · 30-day window

Probes: 1Uptime: 100%Avg latency: 41ms
01

About this API

The interesting part of this API is that it exposes dynamic configuration as explicit configs, variables, waiters, and watch operations rather than a bare key-value store. The resource surface includes "/v1beta1/{name}", "/v1beta1/{name}:watch", "/v1beta1/{parent}/configs", and "/v1beta1/{parent}/variables", with groupings such as "projects".

For backend teams, that is useful when the goal is to publish runtime configuration variables, create waiters for variable changes, or watch config changes from backend jobs. The spec lists scopes such as "https://www.googleapis.com/auth/cloud-platform" and "https://www.googleapis.com/auth/cloudruntimeconfig".

The exposed API version is v1beta1 This is runtime config, not a full secrets-management surface

02

What you can build

  • 1Publish runtime configuration variables
  • 2Create waiters for variable changes
  • 3Watch config changes from backend jobs
03

Strengths & limitations

Strengths

  • Provides concrete variable, waiter, and watch paths
  • Exposes both cloudruntimeconfig and cloud-platform scopes
  • Fits dynamic configuration better than static deploy files

Limitations

  • The exposed API version is v1beta1
  • This is runtime config, not a full secrets-management surface
04

Example request

Generic template — replace <endpoint> with the real path from the docs.
curl https://google.com/<endpoint> \
  -H "Authorization: Bearer $ACCESS_TOKEN"
05

Getting started

Start by listing or creating configs, then validate variables, waiters, and the {name}:watch operation. For change-driven jobs, focus on watch and waiter behavior first.

06

Technical details

CORS: NoHTTPS: YesSignup: YesOpen source: No
Auth type
oauth
Pricing
unknown
Protocols
REST
Response time
41 ms
Last health check
5/12/2026, 7:37:36 AM
07

Tags

08

More from Google