Cloud Run Admin API logo

Cloud Run Admin API

Cloud Run Admin API

Administer Cloud Run services, jobs, executions, revisions, and tasks for container-based workloads.

Visit site ↗Health checked 9h ago
Use it when

Covers services, jobs, executions, and tasks

Watch for

This is a control-plane API, not your app runtime API

First check

Begin with the cloud-platform scope and list services or jobs first, then test run, wait, and executions. If you are building batch orchestration, shape the flow around jobs and executions.

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

Uptime · 30-day window

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

About this API

This is the Cloud Run admin surface for services, jobs, executions, revisions, and tasks, which makes it relevant for teams that automate container deployment and run control. The resource surface includes "/v2/{name}", "/v2/{name}/operations", "/v2/{name}:run", and "/v2/{name}:wait", with groupings such as "projects".

For backend teams, that is useful when the goal is to create or update cloud run services, trigger jobs and track executions, or inspect revisions and tasks for runtime troubleshooting. The spec lists scopes such as "https://www.googleapis.com/auth/cloud-platform".

This is a control-plane API, not your app runtime API Requires cloud-platform scope and project-level permissions

02

What you can build

  • 1Create or update Cloud Run services
  • 2Trigger jobs and track executions
  • 3Inspect revisions and tasks for runtime troubleshooting
03

Strengths & limitations

Strengths

  • Covers services, jobs, executions, and tasks
  • Includes both run and wait actions
  • Uses the Cloud Run Admin API v2 surface

Limitations

  • This is a control-plane API, not your app runtime API
  • Requires cloud-platform scope and project-level permissions
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

Begin with the cloud-platform scope and list services or jobs first, then test run, wait, and executions. If you are building batch orchestration, shape the flow around jobs and executions.

06

Technical details

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

Tags

08

More from Google