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

Autenticação

Envie uma chave de API como um token de portador. A chave deve ter a permissão sites.view; uma chave sem ela é recusada com 403, e não 404.

Este endpoint não requer um ID de organização. Sua chave já identifica a organização à qual pertence, e a resposta é delimitada a ela.

Experimente

Substitua qualquer item entre colchetes por seus próprios valores e o espaço reservado para a chave por uma chave do seu painel.

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

Conectado? O console da API no seu painel preenche o ID da sua organização real e a sua própria chave, e executa a requisição contra a API de produção para que você possa ver a resposta real. Abra este endpoint no console da API

Detalhes

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.

Parâmetros

Resposta

Erros que este endpoint pode retornar

401 · 403 · 404 · 429 · 503