lb.services.deleteDelete a service (listener)
DELETE /lb/api/load-balancers/{id}/services/{serviceId}IAM lb:DeleteServiceChanges stateDestructive
Request syntax
DELETE /lb/api/load-balancers/{id}/services/{serviceId}Path parameters
idRequiredstring
Constraints: uuid
serviceIdRequiredstring
Constraints: uuid
Response
200 with { id }; the provider removes the listener (and an uploaded certificate) in the background. A service id that does not exist also answers 200. 400 when the load balancer 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:DeleteService 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 services delete id serviceIdcurl -X DELETE "https://console.platform-development.deutschecloud.app/lb/api/load-balancers/id/services/serviceId" \
-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_services_delete.