Skip to content
Helicarrier Developers

Attach project dedicated IP

Attach an existing account-owned outbound IP to a project.

PUT /api/projects/{slug}/dedicated-ip HTTPS
Request & response examples
Request example Server-side
curl --fail-with-body --request PUT \
'https://app.helicarrier.xyz/api/projects/my-project/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": []
},
"effective": "within about a minute — no redeploy needed",
"excluded": []
}

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

slug string required

Project slug.

Request body

ipId string required

Dedicated IP id from list_dedicated_ips.

Response 200

Returns the attachment and effective timing. Check excluded for project services that cannot use this IP.

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
effective string

When the attachment starts applying.

excluded array

Project services that cannot use the attachment.

Errors

401

The API key is missing, invalid, or revoked.

403

The caller or key scope does not permit this operation.

Error handling and safe retries
ALSO AVAILABLE VIA MCP

attach_project_dedicated_ip

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

Connect your agent ↗