hosting
POST /v1/sites/{siteId}/scheduled-tasks/{taskId}/run
Run a scheduled task now.
Authentication
Send an API key as a bearer token. The endpoint checks sites.panel_access, sites.view; a key without it is refused with 403, not 404.
This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.
Try it
Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.
curl -X POST https://api.zinndigital.com/v1/sites/{siteId}/scheduled-tasks/{taskId}/run \
-H "Authorization: Bearer zdk_live_…"Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console
Details
Starts the task on its server at once, inside the site's own CageFS, in the background (202). The run is recorded like a scheduled one with trigger: manual and appears in listSiteScheduledTaskRuns within a few seconds. Rate-limited: once a minute per task and 10 times in 10 minutes per account (429 with Retry-After). Refused (422) while the site is not active. Audited as site.cron.run.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
siteId (path) | Uuid | Yes | Site ID (UUIDv7). |
taskId (path) | string | Yes | The task's id from listSiteScheduledTasks: a UUID for a task managed here, or a 16-character id for a line added to the crontab over SSH. |
Errors this endpoint can return
401 · 403 · 404 · 422 · 429 · 503