Schedule an Apify Actor or Task to run on a recurring cron schedule via the Schedules API

Documented steps

1. POST https://api.apify.com/v2/schedules with 'Content-Type: application/json'.
2. Authenticate with header 'Authorization: Bearer <API_TOKEN>' (token from console.apify.com Integrations page). The docs mark the '?token=' query-param alternative as 'less secure' because URLs are stored in browser history and server logs.
3. Required field 'actions': an array of action objects. Each needs a type — RUN_ACTOR (with actorId) or RUN_ACTOR_TASK (with actorTaskId) — and may carry an 'input' object that overrides the target's input for scheduled runs.
4. Set 'cronExpression' using standard five-field cron syntax or a shortcut such as @monthly. Example: "0 8 * * *" for 08:00 daily.
5. Set 'timezone' (for example "UTC" or "America/New_York") so the trigger time is interpreted in the zone you intend.
6. Set 'isEnabled': true. A schedule created without it exists but never fires.
7. Optional: name (3-63 chars), title, description, and isExclusive to prevent a new scheduled run from starting while the previous one is still going.
8. Minimal body: {"name":"nightly-crawl","cronExpression":"0 8 * * *","timezone":"UTC","isEnabled":true,"actions":[{"type":"RUN_ACTOR_TASK","actorTaskId":"<taskId>"}]}
9. The 201 response returns the schedule object including its id and a computed nextRunAt. Manage it afterwards with GET/PUT/DELETE /v2/schedules/{scheduleId}, and inspect firing history via the schedule's log endpoint.
10. Docs: https://docs.apify.com/platform/schedules and https://docs.apify.com/api/v2/schedules-post