Set automatic deployments

Enable or disable automatic deployments when the tracked Git source changes.

PATCH /api/services/{id}/autodeploy HTTPS

Request & response examples

Request example Server-side

curl --fail-with-body --request PATCH \
  'https://app.helicarrier.xyz/api/services/YOUR_ID/autodeploy' \
  -H "Authorization: Bearer $HELI_API_KEY" \
  -H 'Content-Type: application/json' \
  --data '{
  "enabled": true
}'

const response = await fetch(
  "https://app.helicarrier.xyz/api/services/YOUR_ID/autodeploy",
  {
    method: "PATCH",
    headers: {
      Authorization: `Bearer ${process.env.HELI_API_KEY}`,
      "Content-Type": "application/json"
    },
    body: JSON.stringify({
      "enabled": true
    })
  }
);
const data = await response.json();
if (!response.ok) {
  throw new Error(`HTTP ${response.status}: ${data.error}`);
}
// Inspect data; avoid logging secret responses.

import os
import requests

response = requests.request(
    "PATCH",
    "https://app.helicarrier.xyz/api/services/YOUR_ID/autodeploy",
    headers={
        "Authorization": f"Bearer {os.environ['HELI_API_KEY']}"
    },
    json={
      "enabled": True
    },
    timeout=30,
)
response.raise_for_status()
data = response.json()
# Inspect data; avoid logging secret responses.

Response example 200

{
  "id": "svc_example",
  "name": "my-app",
  "slug": "my-app",
  "sourceType": "image",
  "status": "running",
  "planKey": "heli-s1",
  "projectId": "prj_example",
  "environmentId": "env_example",
  "autoDeploy": true
}

Illustrative values · selected fields

Response details ↓ OpenAPI ↗

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

id string required

Service id.

Request body application/json

enabled boolean required

true to enable auto-deploy.

Response 200

Returns the service with the saved automatic-deployment setting. This controls future matching Git pushes.

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

id string

Unique identifier of this resource.

name string

Human-readable resource name.

slug string

URL-safe resource identifier.

sourceType string

Source used to build or run the service.

status string

Current state of the resource or operation.

planKey string

Plan identifier from the plan catalog.

projectId string

Project that owns the resource.

environmentId string

Environment that contains the service.

autoDeploy boolean

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

`set_autodeploy`

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

Connect your agent ↗

curl --fail-with-body --request PATCH \ 'https://app.helicarrier.xyz/api/services/YOUR_ID/autodeploy' \ -H "Authorization: Bearer $HELI_API_KEY" \ -H 'Content-Type: application/json' \ --data '{ "enabled": true }'

import os import requests response = requests.request( "PATCH", "https://app.helicarrier.xyz/api/services/YOUR_ID/autodeploy", headers={ "Authorization": f"Bearer {os.environ['HELI_API_KEY']}" }, json={ "enabled": True }, timeout=30, ) response.raise_for_status() data = response.json() # Inspect data; avoid logging secret responses.

{ "id": "svc_example", "name": "my-app", "slug": "my-app", "sourceType": "image", "status": "running", "planKey": "heli-s1", "projectId": "prj_example", "environmentId": "env_example", "autoDeploy": true }