Skip to content
Helicarrier Developers

Restore service

Restore an eligible deleted service and redeploy it with its retained configuration.

POST /api/services/{id}/restore HTTPS
Request & response examples
Request example Server-side
curl --fail-with-body --request POST \
'https://app.helicarrier.xyz/api/services/YOUR_ID/restore' \
-H "Authorization: Bearer $HELI_API_KEY"
Response example 200
{
"status": "restored",
"id": "svc_example",
"slug": "my-app"
}

Illustrative values · selected fields

Authorization

An account key with access, or a project key with project:write. A service key cannot perform this operation.

Authorization: Bearer <key> Key setup ↗

Path parameters

id string required

Service id.

Response 200

Restores an eligible deleted service and redeploys it. The restored identifier is the same; inspect the service to follow recovery.

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

status string

Current state of the resource or operation.

id string

Unique identifier of this resource.

slug string

URL-safe resource identifier.

Errors

401

The API key is missing, invalid, or revoked.

403

The caller or key scope does not permit this operation.

404

The resource does not exist or is not visible to this caller.

500

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

Error handling and safe retries
ALSO AVAILABLE VIA MCP

restore_service

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

Connect your agent ↗