---
title: "Creates a load balancer in the project and returns the async operation."
method: POST
path: "/projects/{project_id}/networking/internal-load-balancers"
tags: ["Internal Load Balancers"]
---

# Creates a load balancer in the project and returns the async operation.

`POST /projects/{project_id}/networking/internal-load-balancers`

## Path parameters

- `project_id` string, required

## Request body

- LoadBalancersPostRequest
  - `algorithm` string, required — Load balancing algorithm used to distribute traffic across destinations (for example, random).
  - `destinations` NetworkTarget[], required — Backend targets the load balancer forwards traffic to, given as CIDR blocks or resource IDs.
    - `cidr` string — CIDR block, or an IP address that is converted to a CIDR. Mutually exclusive with resource_id.
    - `resource_id` string — ID of a backend resource. Mutually exclusive with cidr.
  - `health_check` HealthCheckOptions
    - `failure_count` string — Number of allowed failures before considering a backend unhealthy.
    - `interval` string — Interval between health checks, in seconds.
    - `port` string, required — Port on which to perform health checks.
    - `success_count` string — Number of successful checks required to consider a backend healthy.
    - `timeout` string — Timeout for a health check response, in seconds.
  - `location` string, required — Location to create the load balancer in.
  - `name` string, required — Name for the new load balancer.
  - `network_interfaces` LoadBalancerNetworkInterface[], required — Network interfaces to attach the load balancer to.
    - `network` string — ID of the VPC network for the interface.
    - `subnet` string — ID of the subnet for the interface.
  - `protocols` string[], required — Network protocols the load balancer handles. Currently only one of: tcp, udp.
  - `type` string — Type of the load balancer (for example, internal_ipv4).

## Response `200`

- AsyncOperationResponse
  - `operation` Operation, required — Individual resources that use Operations should populate the `metadata` field with resource-specific information.
    - `completed_at` string, required
    - `metadata` string, required
    - `operation_id` string, required
    - `result` string
    - `started_at` string, required
    - `state` 'IN_PROGRESS' | 'SUCCEEDED' | 'FAILED', required

## Other responses

- `400` — Error Bad Request
- `401` — Error Authentication Failed
- `403` — Error Permissions
- `500` — Error Internal Server

---

[API](https://skmtc.net/crusoecloud/apis/crusoe-cloud-api-gateway.md) · [All operations](https://skmtc.net/crusoecloud/apis/crusoe-cloud-api-gateway/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/crusoecloud/crusoe-cloud-api-gateway/revisions/a3fd2dedc72b/schema)