Skip to content

Delete a DynDNS configuration

DELETE /api/v2/domains/{id}/dyndns/{configId}

Deletes one DynDNS configuration and its update log. The token stops working at once. The A or AAAA record the configuration last set stays in the DNS zone.

Authentication: An API key with the scope write:domains. About keys and scopes

Request

Path parameters

idstringrequired
The domain ID (dom_…).
configIdstringrequired
The DynDNS configuration ID (ddns_…) from configs[].id on GET /api/v2/domains/{id}/dyndns.

Example

DELETE /api/v2/domains/{id}/dyndns/{configId}
curl -X DELETE "https://cloud.hostup.se/api/v2/domains/dom_01hxa3b4c5d6e7f8g9h0j1k2m3/dyndns/ddns_01hxa3b4c5d6e7f8g9h0j1k2m3" \
-H "Authorization: Bearer $HOSTUP_API_KEY"

Responses

204 The configuration was deleted. No response body.

Errors

Errors are Problem Details with a stable code. Branch on the code, not on the text.

401Unauthorized. Authentication is required.
403Forbidden. The caller lacks a required scope or does not own the resource.
404The domain or the configuration was not found. code is domain_not_found for the domain, dyndns_config_not_found for an unknown configuration ID, and not_found for a configuration that was deleted or is not on this domain. A repeated DELETE of the same ID returns 404 not_found; treat it as deleted.
429Rate limited. Retry after the limit resets. 429 responses include Retry-After seconds plus X-RateLimit-* headers.
500Internal error. Retry later or contact support if the issue persists.