Skip to content
HelicarrierDevelopers

Update cron schedule

Update a cron service’s schedule or command.

PATCH/api/services/{id}/scheduleHTTPS
Request & response examples
Request exampleServer-side
curl --fail-with-body --request PATCH \
'https://app.helicarrier.xyz/api/services/YOUR_ID/schedule' \
-H "Authorization: Bearer $HELI_API_KEY" \
-H 'Content-Type: application/json' \
--data '{
"schedule": "0 9 * * *"
}'
Response example200
{
"id": "svc_example",
"name": "my-app",
"slug": "my-app",
"sourceType": "image",
"status": "running",
"planKey": "heli-s1",
"projectId": "prj_example",
"environmentId": "env_example",
"schedule": "0 9 * * *",
"startCommand": "npm run daily-job"
}

Illustrative values · selected fields

Authorization

An account key with access, or a project/service key with settings:write. The resource must be within the key’s project, service, and environment scope.

Authorization: Bearer <key>Key setup

Path parameters

idstringrequired

Cron service id.

Request body

schedulestringrequired

Crontab expression.

commandstringoptional

Command to run.

Response 200

Returns the updated service. The scheduler is updated immediately; a deployment is not needed just to change the schedule.

Examples show selected response fields with illustrative values. Your response can contain additional fields.

idstring

Unique identifier of this resource.

namestring

Human-readable resource name.

slugstring

URL-safe resource identifier.

sourceTypestring

Source used to build or run the service.

statusstring

Current state of the resource or operation.

planKeystring

Plan identifier from the plan catalog.

projectIdstring

Project that owns the resource.

environmentIdstring

Environment that contains the service.

schedulestring

Cron expression.

startCommandstring

Errors

400

Invalid parameters. Check the required fields, types, and resource configuration.

401

The API key is missing, invalid, or revoked.

403

The caller or key scope does not permit this operation.

500

The operation could not be completed. Check resource state before retrying a write.

Error handling and safe retries
ALSO AVAILABLE VIA MCP

update_cron

Required MCP arguments: id, schedule. Send path, query, and body fields together as tool arguments.

Connect your agent