Detach Dedicated Ip Endpoints

Detach Dedicated IP from Endpoint

DELETE /v1/endpoints/{uuid}/dedicated-ip

Release the dedicated IP from this endpoint. The IP itself is not released back to the platform pool — it's still allocated to your account and shows up in /dedicated-ips as unattached, ready to be re-attached to another endpoint or released entirely via /dedicated-ips/{id}/release.

The endpoint's hostname reverts to the global CNAME target (GeoDNS). DNS propagation takes 1-2 minutes; some clients may continue resolving to the old dedicated IP until their TTL expires.

If your customers' firewalls have allow-listed the dedicated IP, they'll start failing once propagation is complete. Coordinate the swap.

This detaches a single IP only. To detach a per-region group instead, use DELETE /v1/endpoints/{uuid}/dedicated-ip-group.

Path parameters

uuid string (uuid) Req

Endpoint UUID.

Response (204 No Content)

Empty body on success. The call is idempotent: detaching an endpoint that has no dedicated IP attached also returns 204.

Errors

401 Unauthorized

Missing auth.

404 Not Found

Endpoint doesn't exist or doesn't belong to your tenant.

502 Bad Gateway

DNS repoint failed after the binding was cleared — the change is automatically reverted; safe to retry.

Request
curl -X DELETE "https://api.ngris.com/v1/endpoints/<uuid>/dedicated-ip" \
  -H "X-API-KEY: <your_api_key>"

Python
from ngris import Ngris

client = Ngris(api_key="<your_api_key>")
client._delete_void("/endpoints/<endpoint_uuid>/dedicated-ip")

Response — 204 No Content

PreviousAttach Dedicated IP NextAttach Dedicated IP Group

On this page

Detach Dedicated IP from Endpoint