lb.load-balancers.listList load balancers
GET /lb/api/load-balancersIAM lb:DescribeLoadBalancersRead
Request syntax
GET /lb/api/load-balancersResponse
200 with the organization’s load balancers, oldest first, each: id, name, type, algorithm, regionId, status (provisioning, active, deleting, error), reconcileError, ipv4, ipv6, hostname, scheme, vpcId, webAclId, managedBy, managedById, createdAt, … . Includes the ones other services own (managedBy set). The console narrows the list to its selected project; the API returns all.
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:DescribeLoadBalancers 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 listcurl -X GET "https://console.platform-development.deutschecloud.app/lb/api/load-balancers" \
-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_list.