Scheduler APIs
Scheduled job management for tenant applications — cron, one-shot, and recurring-interval schedules that invoke an HTTP target on a timer.
The Scheduler Gateway is the external-facing entry point. It derives the
request context from ingress headers (x-user-id, x-tenant-id,
x-user-email) and forwards each call to the internal SchedulerService,
which persists schedule state and drives execution on top of
River and Cloud SQL Postgres.
All endpoints use POST /api/v1/scheduler/<method> with a JSON request
body. Request and response bodies use protojson encoding (the JSON
representation of Protocol Buffer messages): enum fields are serialized as
their string names and timestamps as RFC 3339 strings.
See the Scheduled Jobs guide for concepts, examples, and retry behaviour.
Authentication
- HTTP: Bearer Auth
- API Key: apiKeyAuth
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |
Bearer format: | JWT |
Security Scheme Type: | apiKey |
|---|---|
Header parameter name: | X-API-Key |