GET /v1/sites/{siteId}/scheduled-tasks

Authentication

Send an API key as a bearer token. The key must carry the sites.view permission; 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 GET https://api.zinndigital.com/v1/sites/{siteId}/scheduled-tasks \
  -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

The site's scheduled tasks (cron jobs): name, kind, what it runs, the schedule (UTC), whether it is on, and why it is paused if it is. Tasks managed here come first (source: panel); lines added to the crontab over SSH follow (source: crontab, read-only — they can be deleted here but are never rewritten by us). kinds lists what this site may run (wpcron only on WordPress, php not on a static site). limit_per_site/limit_per_org and used/used_in_org are the counts behind can_create; permitted is whether the plan includes scheduled tasks at all — "your plan does not include this" is not "you have used them all". Available on every hosting line whose site runs on our own servers. A task runs as the site's own user, inside its CageFS, from the site folder, and is stopped after 15 minutes. While the site is suspended its tasks are switched off on the server and come back when it is active again. Requires sites.view and sites.panel_access; 404 for a site not on our own servers.

Parameters

Response

Errors this endpoint can return

401 · 403 · 404 · 422 · 429 · 503