Skip to content
Helicarrier Developers

Roll back a service

Queue a deployment using a retained image from an earlier release.

POST /api/services/{id}/rollback/{deploymentId} HTTPS
Request & response examples
Request example Server-side
curl --fail-with-body --request POST \
'https://app.helicarrier.xyz/api/services/YOUR_ID/rollback/YOUR_DEPLOYMENT_ID' \
-H "Authorization: Bearer $HELI_API_KEY"
Response example 202
{
"deploymentId": "dep_example"
}

Illustrative values · selected fields

Authorization

An account key with access, or a project/service key with deployments: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.

deploymentId string required

Deployment to roll back to (must be within the rollback window).

Response 202

Queues a deployment using the retained image from the selected release. Follow the new deploymentId; application rollback does not restore database data.

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

deploymentId string

Identifier to use when reading deployment history or logs.

Errors

401

The API key is missing, invalid, or revoked.

403

The caller or key scope does not permit this operation.

409

The current resource state prevents the operation. Inspect it before retrying.

410

The request could not be completed.

Error handling and safe retries
ALSO AVAILABLE VIA MCP

rollback_service

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

Connect your agent ↗