Skip to content
Helicarrier Developers

Attach service dedicated IP

Attach an existing account-owned outbound IP to a service. A deployment is required to apply it.

PUT /api/services/{id}/dedicated-ip HTTPS
Request & response examples
Request example Server-side
curl --fail-with-body --request PUT \
'https://app.helicarrier.xyz/api/services/YOUR_ID/dedicated-ip' \
-H "Authorization: Bearer $HELI_API_KEY" \
-H 'Content-Type: application/json' \
--data '{
"ipId": "YOUR_IP_ID"
}'
Response example 200
{
"ip": {
"id": "ip_example",
"address": "203.0.113.10",
"label": "Production",
"attachments": []
},
"redeployRequired": true,
"effective": "on the service's next deploy"
}

Illustrative values · selected fields

Authorization

An account key with access to the resource. Project and service keys do not authorize this operation.

Authorization: Bearer <key> Key setup ↗

Path parameters

id string required

Service id.

Request body

ipId string required

Dedicated IP id from list_dedicated_ips.

Response 200

Returns the service attachment. Deploy the service again to apply the new outbound address.

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

ip object

Attached dedicated IP, or null when detached. In DNS responses, the target IP address.

Child fields
  • id string

    Unique identifier of this resource.

  • address string
  • label string

    Human-readable label.

  • attachments array
redeployRequired boolean

Whether another service deployment is required.

effective string

When the attachment starts applying.

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.

Error handling and safe retries
ALSO AVAILABLE VIA MCP

attach_service_dedicated_ip

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

Connect your agent ↗