hosting
GET /v1/sites/{siteId}/scheduled-tasks
List a site's scheduled tasks.
Аутентификација
Пошаљите API кључ као bearer токен. Кључ мора имати дозволу sites.view; кључ без ње се одбија уз 403, а не 404.
Ова крајња тачка не прихвата id организације. Ваш кључ већ идентификује организацију којој припада, а одговор је ограничен на њу.
Испробајте
Замените све што је у угластим заградама сопственим вредностима, а чувар места кључа кључем са своје контролне табле.
curl -X GET https://api.zinndigital.com/v1/sites/{siteId}/scheduled-tasks \
-H "Authorization: Bearer zdk_live_…"Пријављени сте? API конзола на вашој контролној табли попуњава ваш прави id организације и ваш сопствени кључ, и покреће захтев према живом API-ју како бисте могли да видите стварни одговор. Отворите ову крајњу тачку у API конзоли
Детаљи
The cron jobs on the site's hosting package: when each runs, what it runs, whether it is paused, and where its output is mailed. schedule is the customer's own crontab expression carried verbatim — a customer who typed */15 * * * * sees exactly that back, never a normalised rewriting of it. permitted and can_create answer the two different questions a screen must distinguish before it offers an "add" button: "your plan does not include this" is not "you have used all of them". ⛔ the platform publishes scheduled tasks as a boolean capability with no count, so limit is normally unlimited and can_create follows permitted rather than an arithmetic on a ceiling nobody published. Requires sites.view and sites.panel_access — a cron row is a filesystem path plus a command run as the site's user, which is the same access the file manager that key already gates. ⭐ Available on both a resold hosting package and a site on Zinn®'s own fleet, including Footprint-Free. That matters for a footprint site in particular: WordPress's own scheduler only fires when somebody visits, and a footprint site by design has very few visitors, so its scheduled publishing and index-ping jobs would otherwise run late or not at all. Every fleet site is given a real system cron entry at deploy, and the jobs listed here are the customer's own — the platform's are held separately and are never listed, edited or deleted through this endpoint.
Параметри
| Назив | Тип | Обавезно | Шта је ово |
|---|---|---|---|
siteId (path) | Uuid | Да | Site ID (UUIDv7). |
Одговор
| Назив | Тип | Обавезно | Шта је ово |
|---|---|---|---|
data | SiteScheduledTask[] | Да | The cron jobs on the package. |
limit | VendorAllowance | Да | The effective ceiling on scheduled tasks. ⛔ the platform publishes this capability as a boolean with no count, so it is normally unlimited — can_create must not be derived… |
permitted | boolean | Да | Whether the package type includes scheduled tasks at all. |
can_create | boolean | Да | permitted, and the effective ceiling has room. |
Грешке које ова крајња тачка може вратити
401 · 403 · 404 · 429 · 503