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

Pagpapatotoo

Magpadala ng API key bilang isang bearer token. Kailangang taglayin ng key ang pahintulot na sites.view; ang key na wala nito ay tatanggihan gamit ang 403, hindi 404.

Ang endpoint na ito ay hindi nangangailangan ng id ng organisasyon. Natutukoy na ng iyong key ang organisasyong kinabibilangan nito, at nakatuon ang tugon dito.

Subukan ito

Palitan ang anuman sa loob ng mga panaklong na may anggulo ng iyong sariling mga halaga, at ang placeholder ng key na may key mula sa iyong dashboard.

curl -X GET https://api.zinndigital.com/v1/sites/{siteId}/scheduled-tasks \
  -H "Authorization: Bearer zdk_live_…"

Nakalagda? Ang API console sa iyong dashboard ay awtomatikong naglalagay ng iyong tunay na ID ng organisasyon at sariling susi, at pinapatakbo ang kahilingan laban sa live na API upang makita mo ang aktwal na tugon. Buksan ang endpoint na ito sa console ng API

Mga Detalye

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.

Mga Parameter

Tugon

Mga error na maibabalik ng endpoint na ito

401 · 403 · 404 · 429 · 503