Attach Dedicated IP Group to Endpoint
Attach a per-region dedicated-IP group (provisioned via POST /v1/dedicated-ips/requests with selection_mode: "per_region") to an endpoint. The platform publishes the endpoint as a CNAME to the group's geolocation FQDN (grp-<group uuid> under the platform's geo zone), so visitors resolve to the nearest regional IP in the group.
A group binding is mutually exclusive with a single dedicated IP: attaching a group clears any single-IP binding (and attaching a single IP clears the group binding). DNS propagation typically takes 1-2 minutes after attach.
List your groups with GET /v1/dedicated-ips/groups and detach with DELETE /v1/endpoints/{uuid}/dedicated-ip-group.
Path parameters
Request body
uuid of an active per-region group allocated to your account. Get it from /dedicated-ips/groups. The group must be in active status and belong to your account.Deprecated: group_id (integer) is still accepted until the sunset. Send group_uuid; sending both for different objects is a 400 id_uuid_mismatch.
Response (200 OK)
uuid (echo).uuid of the group now bound to this endpoint (echo).grp-<group uuid>.<geo-zone>.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
group_uuid, a malformed group_uuid, group_id and group_uuid naming different groups (id_uuid_mismatch), invalid JSON, or an agentless (static hosting) endpoint.dedicated_ips entitlement, or your role can't update dedicated IPs.active.