Get cron configuration
Read a cron service’s schedule, command, and next expected run.
Request & response examples
Request example Server-side
curl --fail-with-body --request GET \ 'https://app.helicarrier.xyz/api/services/YOUR_ID/cron' \ -H "Authorization: Bearer $HELI_API_KEY"const response = await fetch( "https://app.helicarrier.xyz/api/services/YOUR_ID/cron", { method: "GET", headers: { Authorization: `Bearer ${process.env.HELI_API_KEY}` } });const data = await response.json();if (!response.ok) { throw new Error(`HTTP ${response.status}: ${data.error}`);}// Inspect data; avoid logging secret responses.import osimport requests
response = requests.request( "GET", "https://app.helicarrier.xyz/api/services/YOUR_ID/cron", headers={ "Authorization": f"Bearer {os.environ['HELI_API_KEY']}" }, timeout=30,)response.raise_for_status()data = response.json()# Inspect data; avoid logging secret responses. Response example 200
{ "schedule": "0 9 * * *", "command": "npm run daily-job", "nextRun": "2026-10-08T09:00:00Z", "scheduleValid": true}Illustrative values · selected fields
Path parameters
id string required Cron service id.
Response 200
Returns the saved schedule, command, next run time, and schedule validity. nextRun can be null when no next run can be calculated.
Examples show selected response fields with illustrative values. Your response can contain additional fields.
schedule string Cron expression.
command string Command executed by the scheduled service.
nextRun string Next scheduled run timestamp, or null.
scheduleValid boolean Whether the saved schedule can be parsed.
Errors
401 The API key is missing, invalid, or revoked.
403 The caller or key scope does not permit this operation.
ALSO AVAILABLE VIA MCP
Connect your agent ↗ get_cron
Required MCP arguments: id. Send path, query,
and body fields together as tool arguments.