capExpertAPI · Cloud Scheduler · updated 21 October 2026

CapExpert cron jobs

Every cron runs as a job named in the request body. With CAP-247 each Scheduler entry keeps its name and schedule but moves from POST /worker to POST /cron-worker on the import API, with its job renamed to end in CronJob. Dev is repointed (21 Oct); prod moves at the CAP-247 prod deploy, and Prod now shows what it runs until then. Open an environment for its full list, with copy buttons on every URL, description and body.

Environments

Dev cron jobsimport-api-dev.capexpert.io/api/v1/cron-worker
    Open dev →     Prod cron jobsimport-api.capexpert.io/api/v1/cron-worker
      Open prod →       Prod now, before CAP-247what runs on /worker today · read Oct 13
        Open current prod →

        Every entry

        shared by every scheduler entry
        Method
        HTTP · POST
        Headers
        Accept: application/json · Content-Type: application/json · User-Agent: Google-Cloud-Scheduler
        Auth header
        Add OIDC token. Audience empty, or exactly the entry’s URL
        Body
        { "jobName": "<Name>CronJob", "payload": {} }