Google Cloud Scheduler API
Browse all Google APIs✓ Official Vendor SpecDeveloper ToolsCi Cdoauth210 EndpointsREST
For Agents
Schedule recurring HTTP, App Engine, or Pub/Sub jobs using cron expressions and pause, resume, or trigger them on demand. Lets agents own time-based automation across GCP without standing up a cron host.
Use for: I need to schedule a job to run every hour, Create a Cloud Scheduler job that triggers an HTTP endpoint nightly, Pause a scheduled job before maintenance, Resume a paused Cloud Scheduler job
Not supported: Does not run user code, queue ad-hoc tasks, or orchestrate multi-step workflows — use for time-based recurring triggers against HTTP, App Engine, or Pub/Sub targets only.
Cloud Scheduler is a fully managed enterprise-grade cron service for Google Cloud. The API lets you create, update, pause, resume, and run jobs that fire HTTP, App Engine, or Pub/Sub targets on a recurring schedule defined with standard cron syntax. It handles retries with exponential backoff and reports per-job execution state, replacing fragile self-hosted cron servers for batch ETL, billing rollups, and timed agent workflows.
Install Jentic One Beta
Connect the Cloud Scheduler API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cloud Scheduler API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Cloud Scheduler API.
Create scheduled jobs that target HTTP endpoints, App Engine handlers, or Pub/Sub topics
Pause and resume jobs around release windows or incident response
Trigger a queued job to run immediately for testing or backfill
Configure retry policy with exponential backoff and max attempts per job
List and delete jobs across regions in a project
Use Cases
Patterns agents use Cloud Scheduler API for, with concrete tasks.
★ Cron-Driven HTTP Webhooks
Replace self-managed cron boxes with managed schedules that POST to any reachable HTTPS endpoint. Cloud Scheduler signs the request with an OIDC or OAuth token from a service account and retries on failure with configurable backoff, making it suitable for nightly billing rollups, cache warmers, and reconciliation jobs that need to run on time without operators.
Create a Cloud Scheduler job that sends a POST to https://api.example.com/reconcile every day at 03:00 UTC with retries enabled
Pub/Sub Fan-Out On a Schedule
Trigger downstream pipelines by publishing a message to a Pub/Sub topic on a fixed cadence. Cloud Scheduler jobs with a Pub/Sub target are ideal for orchestrating Cloud Functions, Cloud Run services, or Dataflow pipelines without coupling them to one another, and the schedule runs in the same region as the consumer to keep latency predictable.
Create a job that publishes {"action": "refresh"} to projects/acme/topics/data-refresh every 15 minutes
Maintenance Window Pausing
Pause and later resume scheduled jobs around release windows or incident response so noisy cron firings do not pile up while a service is down. Cloud Scheduler stores the schedule state separately from the running schedule, letting an agent or runbook flip jobs off and back on with a single API call each.
Pause job projects/acme/locations/us-central1/jobs/billing-rollup, run the deployment, then call resume on the same job
Agent-Triggered Scheduled Workflows
An AI agent can stand up a one-off recurring job to drive its own multi-step workflow — for example, polling a slow-moving data source every 30 minutes and stopping once a condition is met. Through Jentic, the agent searches for 'schedule a recurring job', receives the jobs.create schema, and provisions the job without learning the full Cloud Scheduler resource model.
Use Jentic to create a Cloud Scheduler job that triggers the agent's webhook every 30 minutes and call delete on the job once the workflow completes
Key Endpoints
10 endpoints — cloud scheduler is a fully managed enterprise-grade cron service for google cloud.
METHOD
PATH
DESCRIPTION
GET
/v1/{+name}/locations
List Cloud Scheduler locations available to the project
POST
/v1/{+name}:run
Trigger a job to run immediately
POST
/v1/{+name}:pause
Pause an active scheduled job
POST
/v1/{+name}:resume
Resume a paused job
POST
/v1/{+name}:cancel
Cancel an in-flight job execution
GET
/v1/{+name}/locations
List Cloud Scheduler locations available to the project
POST
/v1/{+name}:run
Trigger a job to run immediately
POST
/v1/{+name}:pause
Pause an active scheduled job
POST
/v1/{+name}:resume
Resume a paused job
POST
/v1/{+name}:cancel
Cancel an in-flight job execution
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Google OAuth 2.0 client credentials and refresh tokens for Cloud Scheduler are stored encrypted in the Jentic vault. Agents only see scoped short-lived access tokens at execution time.
Intent-based discovery
Agents search Jentic with intents like 'schedule a recurring job' and Jentic returns the jobs.create operation with its request schema, so the agent does not need to read Google's discovery document to assemble the call.
Time to first call
Direct integration with Cloud Scheduler: 1-2 days for OAuth setup, region selection, and target configuration. Through Jentic: under 30 minutes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Cloud Scheduler API through Jentic.
What authentication does the Cloud Scheduler API use?
It uses Google OAuth 2.0 with the https://www.googleapis.com/auth/cloud-platform scope. Through Jentic the OAuth client and refresh token live in the Jentic vault and only short-lived access tokens are passed to the agent runtime.
Can I trigger a scheduled job on demand with the Cloud Scheduler API?
Yes. Call the run method on /v1/{name}:run to fire a job immediately outside its normal schedule. This is the standard way to validate a job after creating or editing it.
What are the rate limits for the Cloud Scheduler API?
Google enforces per-project quotas on jobs created and on administrative API calls per minute. Job execution itself is governed by the per-job retry configuration, not by the API quota — most projects can run thousands of jobs concurrently within the default limits.
How do I create a recurring job through Jentic?
Search Jentic for 'schedule a recurring job', load the projects.locations.jobs.create schema, and execute a call against /v1/{parent}/jobs with the cron schedule, target, and timezone. Jentic returns the input schema so the agent fills only the fields it needs.
Is the Cloud Scheduler API free?
Cloud Scheduler offers three free jobs per billing account per month and charges a small monthly fee per additional job. The API itself has no per-call charge beyond the job pricing.
What target types does Cloud Scheduler support?
Each job can target an HTTP or HTTPS endpoint, an App Engine HTTP handler, or a Pub/Sub topic. Use HTTP targets with OIDC tokens to reach private Cloud Run or Cloud Functions services without exposing them publicly.
GET STARTED