प्रमाणीकरण

एपिआई कुञ्जीलाई बियरर टोकन (bearer token) को रूपमा पठाउनुहोस्। कुञ्जीसँग sites.view अनुमति हुनुपर्छ; अनुमति नभएको कुञ्जीलाई 404 होइन, 403 मार्फत अस्वीकार गरिन्छ।

यो इन्डपोइन्टले कुनै संस्थाको आइडी लिँदैन। तपाईंको कुञ्जीले यस अन्तर्गत पर्ने संस्थालाई पहिल्यै पहिचान गर्छ, र प्रतिक्रिया त्यसैमा सीमित हुन्छ।

प्रयास गर्नुहोस्

कोणीय कोष्ठकभित्र भएका जुनसुकै कुरालाई आफ्नो मानहरूद्वारा बदल्नुहोस्, र मुख्य स्थानहोल्डरलाई तपाईंको ड्यासबोर्डको कुञ्जीद्वारा बदल्नुहोस्।

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

लगइन गर्नुभएको छ? तपाईंको ड्यासबोर्डमा रहेको API कन्सोलले तपाईंको वास्तविक संस्थाको आईडी र आफ्नै कुञ्जी भरिदिन्छ, र लाइभ 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).

प्रतिक्रिया

नामप्रकारआवश्यकयो के हो
dataSiteScheduledTask[]हुन्छThe cron jobs on the package.
limitVendorAllowanceहुन्छ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…
permittedbooleanहुन्छWhether the package type includes scheduled tasks at all.
can_createbooleanहुन्छpermitted, and the effective ceiling has room.

यो इन्डपोइन्टले फर्काउन सक्ने त्रुटिहरू

401 · 403 · 404 · 429 · 503