Attach Dedicated IP to Endpoint
Attach a dedicated IP (previously provisioned via /dedicated-ips/requests and fulfilled by the operator) to an endpoint. Once attached, the platform updates DNS so the endpoint's hostname resolves to the dedicated IP instead of the shared anycast pool.
Use cases:
- Allow-listing: customer firewalls that only let traffic in from a specific IP.
- SLA / reputation: avoid getting "noisy neighbor" rate-limits or blocklist entries from shared anycast IPs.
- Compliance: regulators that demand dedicated infrastructure.
Each dedicated IP can be attached to one endpoint at a time. Re-attaching to a different endpoint requires detaching first. DNS propagation typically takes 1-2 minutes after attach.
A single-IP binding is mutually exclusive with a per-region group: attaching a single IP here clears any group binding on the endpoint, and vice-versa.
The IP's region binding lives on the dedicated-IP assignment (region_slug), not on the endpoint — endpoints are region-less. The IP is validated against the allowed CIDR ranges for its own region before the binding is persisted.
Path parameters
Request body
uuid of an active dedicated-IP assignment allocated to your account. Get it from /dedicated-ips. The assignment must be in active status and belong to your account.Deprecated: assignment_id (integer) is still accepted until the sunset. Send assignment_uuid; sending both for different objects is a 400 id_uuid_mismatch.
Response (200 OK)
uuid (echo).uuid of the dedicated-IP assignment now bound to this endpoint (echo).Deprecated: until the sunset this response also carries the legacy integer id and *_id fields. Don't use them; read uuid and the *_uuid fields.
Errors
assignment_uuid, a malformed assignment_uuid, assignment_id and assignment_uuid naming different assignments (id_uuid_mismatch), invalid JSON, or an agentless (static hosting) endpoint.dedicated_ips entitlement, or your role can't update dedicated IPs.active, or the IP fails CIDR validation for its region.