lb.load-balancers.deleteDelete a load balancer
Request syntax
DELETE /lb/api/load-balancers/{id}Path parameters
idRequiredstring
Constraints: uuid
Response
200 with { id } once it is gone: deleted at the provider (lb11/lb21/lb31) or its address released (dedicated) before the call answers, with its services, targets and rules. 502 when the provider refuses; the load balancer is then in status `error` with the reason in reconcileError. 404 when it is not found. A load balancer another service owns (a Kubernetes Service, a database endpoint) is refused with 409: change it through its owner.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Errors
- 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
- 401No credentials, or an access key that is unknown, revoked or expired.
- 403The caller's policies do not allow lb:DeleteLoadBalancer on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
- 404The resource does not exist in your organization.
Examples
The required parameters only, with example values. Replace id and the other placeholders with your own.
dcloud lb load-balancers delete idcurl -X DELETE "https://console.platform-development.deutschecloud.app/lb/api/load-balancers/id" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY"Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_lb_load-balancers_delete.