hosting
GET /v1/sites/{siteId}/scheduled-tasks
List a site's scheduled tasks.
Uwierzytelnianie
Wyślij klucz API jako token bearer. Klucz musi posiadać uprawnienie sites.view; klucz bez niego jest odrzucany z kodem 403, a nie 404.
Ten punkt końcowy nie wymaga identyfikatora organizacji. Twój klucz już identyfikuje organizację, do której należy, a odpowiedź jest do niej ograniczona.
Wypróbuj
Zastąp wszystko w nawiasach ostrych własnymi wartościami, a zastępczy znacznik klucza kluczem ze swojego pulpitu nawigacyjnego.
curl -X GET https://api.zinndigital.com/v1/sites/{siteId}/scheduled-tasks \
-H "Authorization: Bearer zdk_live_…"Zalogowany? Konsola API w Twoim panelu uzupełnia rzeczywiste identyfikator organizacji oraz Twój własny klucz i wykonuje żądanie względem aktywnego API, dzięki czemu możesz zobaczyć rzeczywistą odpowiedź. Otwórz ten punkt końcowy w konsoli API
Szczegóły
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.
Parametry
| Nazwa | Typ | Wymagane | Co to jest |
|---|---|---|---|
siteId (path) | Uuid | Tak | Site ID (UUIDv7). |
Odpowiedź
| Nazwa | Typ | Wymagane | Co to jest |
|---|---|---|---|
data | SiteScheduledTask[] | Tak | The cron jobs on the package. |
limit | VendorAllowance | Tak | 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 | Tak | Whether the package type includes scheduled tasks at all. |
can_create | boolean | Tak | permitted, and the effective ceiling has room. |
Błędy, które ten punkt końcowy może zwrócić
401 · 403 · 404 · 429 · 503