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
active status and belong to your account.Response (200 OK)
Errors
assignment_id (must be > 0) or invalid JSON.dedicated_ips entitlement, or the endpoint/assignment belongs to another tenant.active, or the IP fails CIDR validation for its region.