Use the schedules API to run a deployed workflow on a recurring cron-based interval.
x-api-key.callback_url and callback_secret./v1/schedules/createworkflowparamscron_exprtimezone: optional, default UTCtimeout_seconds: optional, default 900start_url: optional start URL override for browser launchgpu: optional boolean GPU overrideviewport: optional { width, height } viewport overridecallback_url: optionalcallback_secret: optionalskip_callbacks: optional, default falseresidential_proxy: optional residential proxy location objectenabled: optional, default truecallback_url, you must also set callback_secret.startUrl, gpu, and viewport on the workflow definition so they travel with the deploy artifact. Use the schedule-level fields when you need a one-off override, or until the hosted executor applies workflow launch metadata automatically.residential_proxy for recurring workflows that need traffic to originate from a specific residential proxy country, US state, city, ZIP code, or ASN. See Residential proxy locations for the supported fields and combination rules.successschedule/v1/schedules/listenabled: optional boolean filterworkflow: optional workflow-name filterlimit: optional page size, default 50, max 200schedules/v1/schedules/getidschedule/v1/schedules/updateidparams: optionalcron_expr: optionaltimezone: optionaltimeout_seconds: optionalcallback_url: optional string or nullcallback_secret: optional string or nullskip_callbacks: optionalresidential_proxy: optional object or nullenabled: optionalcallback_url and callback_secret to null.
To clear the configured residential proxy location, set residential_proxy to null.schedule/v1/schedules/deleteidsuccessidschedule object returned by the schedules endpoints includes:idworkflowparamscron_exprtimezonetimeout_secondsresidential_proxycallback_urlskip_callbacksenablednext_fire_atlast_fire_atlast_job_idlast_errorconsecutive_failurescreated_atupdated_at