Actions140
- Application Load Balancer Actions
- Contract Actions
- Datacenter Actions
- Firewall Rule Actions
- Image Actions
- IP Block Actions
- Kubernetes Cluster Actions
- LAN Actions
- Load Balancer Actions
- Location Actions
- NAT Gateway Actions
- Network Load Balancer Actions
- NIC Actions
- Node Pool Actions
- Private Cross-Connect Actions
- Request Actions
- Security Group Actions
- Server Actions
- Snapshot Actions
- Target Group Actions
- Volume Actions
Network Load Balancer → Create
AI-generatedSummary
Creates a Network Load Balancer in the specified datacenter, with the provided name and listener and target LAN IDs. Additional fields can configure logging and IP addresses.
Inputs
- Datacenter ID (required) — ID of the datacenter where the load balancer will be created.
- Name (required) — Name for the Network Load Balancer.
- Listener LAN (required) — ID of the inbound LAN.
- Target LAN (required) — ID of the private outbound LAN to which traffic is balanced.
- Additional Fields — Optionally enable central logging, provide comma-separated load balancer IPs or private IPs with subnet masks, and specify a logging format.
- Include Request Status — When enabled, include the request tracking ID and status URL returned for the asynchronous operation.
- Include Response Headers — When enabled, include response headers and status code; the response body is nested under
body. - Request Options — Configure batching, SSL certificate validation, an HTTP proxy, or the request timeout.
Output shape
A single API response item describing the created Network Load Balancer.
The source pack contains no operation implementation body, so the response shape cannot be confirmed from source. Enable Include Response Headers to receive the body nested alongside headers and statusCode; Include Request Status can add request tracking details.