---
title: "Create a New Load Balancer"
method: POST
path: "/v2/load_balancers"
tags: ["DigitalOcean-public.v2-new_Load Balancers"]
---

# Create a New Load Balancer

`POST /v2/load_balancers`

To create a new load balancer instance, send a POST request to
`/v2/load_balancers`.

You can specify the Droplets that will sit behind the load balancer using one
of two methods:

* Set `droplet_ids` to a list of specific Droplet IDs.
* Set `tag` to the name of a tag. All Droplets with this tag applied will be
  assigned to the load balancer. Additional Droplets will be automatically
  assigned as they are tagged.

These methods are mutually exclusive.

## Request body

- union
  - object
    - `droplet_ids` integer[], required — An array containing the IDs of the Droplets assigned to the load balancer.
    - `region` 'ams1' | 'ams2' | 'ams3' | 'blr1' | 'fra1' | 'lon1' | 'nyc1' | 'nyc2' | 'nyc3' | 'sfo1' | 'sfo2' | 'sfo3' | 'sgp1' | 'tor1' | 'syd1', required — The slug identifier for the region where the resource will initially be available.
    - `id` string, uuid — A unique ID that can be used to identify and reference a load balancer.
    - `name` string — A human-readable name for a load balancer instance.
    - `project_id` string — The ID of the project that the load balancer is associated with. If no ID is provided at creation, the load balancer associates with the user's default project. If an invalid project ID is provided, the load balancer will not be created.
    - `ip` string — An attribute containing the public-facing IP address of the load balancer.
    - `ipv6` string — An attribute containing the public-facing IPv6 address of the load balancer.
    - `size_unit` integer — How many nodes the load balancer contains. Each additional node increases the load balancer's ability to manage more connections. Load balancers can be scaled up or down, and you can change the number of nodes after creation up to once per hour. This field is currently not available in the AMS2, NYC2, or SFO1 regions. Use the `size` field to scale load balancers that reside in these regions.
    - `size` 'lb-small' | 'lb-medium' | 'lb-large' — This field has been replaced by the `size_unit` field for all regions except in AMS2, NYC2, and SFO1. Each available load balancer size now equates to the load balancer having a set number of nodes. * `lb-small` = 1 node * `lb-medium` = 3 nodes * `lb-large` = 6 nodes You can resize load balancers after creation up to once per hour. You cannot resize a load balancer within the first hour of its creation.
    - `algorithm` 'round_robin' | 'least_connections' — This field has been deprecated. You can no longer specify an algorithm for load balancers.
    - `status` 'new' | 'active' | 'errored' — A status string indicating the current state of the load balancer. This can be `new`, `active`, or `errored`.
    - `created_at` string, date-time — A time value given in ISO8601 combined date and time format that represents when the load balancer was created.
    - `forwarding_rules` ForwardingRule[], required — An array of objects specifying the forwarding rules for a load balancer.
      - `entry_protocol` 'http' | 'https' | 'http2' | 'http3' | 'tcp' | 'udp', required — The protocol used for traffic to the load balancer. The possible values are: `http`, `https`, `http2`, `http3`, `tcp`, or `udp`. If you set the `entry_protocol` to `udp`, the `target_protocol` must be set to `udp`. When using UDP, the load balancer requires that you set up a health check with a port that uses TCP, HTTP, or HTTPS to work properly.
      - `entry_port` integer, required — An integer representing the port on which the load balancer instance will listen.
      - `target_protocol` 'http' | 'https' | 'http2' | 'tcp' | 'udp', required — The protocol used for traffic from the load balancer to the backend Droplets. The possible values are: `http`, `https`, `http2`, `tcp`, or `udp`. If you set the `target_protocol` to `udp`, the `entry_protocol` must be set to `udp`. When using UDP, the load balancer requires that you set up a health check with a port that uses TCP, HTTP, or HTTPS to work properly.
      - `target_port` integer, required — An integer representing the port on the backend Droplets to which the load balancer will send traffic.
      - `certificate_id` string — The ID of the TLS certificate used for SSL termination if enabled.
      - `tls_passthrough` boolean — A boolean value indicating whether SSL encrypted traffic will be passed through to the backend Droplets.
    - `health_check` HealthCheck — An object specifying health check settings for the load balancer.
      - `protocol` 'http' | 'https' | 'tcp' — The protocol used for health checks sent to the backend Droplets. The possible values are `http`, `https`, or `tcp`.
      - `port` integer — An integer representing the port on the backend Droplets on which the health check will attempt a connection.
      - `path` string — The path on the backend Droplets to which the load balancer instance will send a request.
      - `check_interval_seconds` integer — The number of seconds between between two consecutive health checks.
      - `response_timeout_seconds` integer — The number of seconds the load balancer instance will wait for a response until marking a health check as failed.
      - `unhealthy_threshold` integer — The number of times a health check must fail for a backend Droplet to be marked "unhealthy" and be removed from the pool.
      - `healthy_threshold` integer — The number of times a health check must pass for a backend Droplet to be marked "healthy" and be re-added to the pool.
    - `sticky_sessions` StickySessions — An object specifying sticky sessions settings for the load balancer.
      - `type` 'cookies' | 'none' — An attribute indicating how and if requests from a client will be persistently served by the same backend Droplet. The possible values are `cookies` or `none`.
      - `cookie_name` string — The name of the cookie sent to the client. This attribute is only returned when using `cookies` for the sticky sessions type.
      - `cookie_ttl_seconds` integer — The number of seconds until the cookie set by the load balancer expires. This attribute is only returned when using `cookies` for the sticky sessions type.
    - `redirect_http_to_https` boolean — A boolean value indicating whether HTTP requests to the load balancer on port 80 will be redirected to HTTPS on port 443.
    - `enable_proxy_protocol` boolean — A boolean value indicating whether PROXY Protocol is in use.
    - `enable_backend_keepalive` boolean — A boolean value indicating whether HTTP keepalive connections are maintained to target Droplets.
    - `http_idle_timeout_seconds` integer — An integer value which configures the idle timeout for HTTP requests to the target droplets.
    - `vpc_uuid` string, uuid — A string specifying the UUID of the VPC to which the load balancer is assigned.
    - `disable_lets_encrypt_dns_records` boolean — A boolean value indicating whether to disable automatic DNS record creation for Let's Encrypt certificates that are added to the load balancer.
    - `firewall` LbFirewall — An object specifying allow and deny rules to control traffic to the load balancer.
      - `deny` string[] — the rules for denying traffic to the load balancer (in the form 'ip:1.2.3.4' or 'cidr:1.2.0.0/16')
      - `allow` string[] — the rules for allowing traffic to the load balancer (in the form 'ip:1.2.3.4' or 'cidr:1.2.0.0/16')
    - `network` 'EXTERNAL' | 'INTERNAL' — A string indicating whether the load balancer should be external or internal. Internal load balancers have no public IPs and are only accessible to resources on the same VPC network. This property cannot be updated after creating the load balancer.
    - `network_stack` 'IPV4' | 'DUALSTACK' — A string indicating whether the load balancer will support IPv4 or both IPv4 and IPv6 networking. This property cannot be updated after creating the load balancer.
    - `type` 'REGIONAL' | 'REGIONAL_NETWORK' | 'GLOBAL' — A string indicating whether the load balancer should be a standard regional HTTP load balancer, a regional network load balancer that routes traffic at the TCP/UDP transport layer, or a global load balancer.
    - `domains` Domains[] — An array of objects specifying the domain configurations for a Global load balancer.
      - `name` string — FQDN to associate with a Global load balancer.
      - `is_managed` boolean — A boolean value indicating if the domain is already managed by DigitalOcean. If true, all A and AAAA records required to enable Global load balancers will be automatically added.
      - `certificate_id` string — The ID of the TLS certificate used for SSL termination.
    - `glb_settings` GlbSettings — An object specifying forwarding configurations for a Global load balancer.
      - `target_protocol` 'http' | 'https' | 'http2' — The protocol used for forwarding traffic from the load balancer to the target backends. The possible values are `http`, `https` and `http2`.
      - `target_port` integer — An integer representing the port on the target backends which the load balancer will forward traffic to.
      - `cdn` object — An object specifying CDN configurations for a Global load balancer.
        - `is_enabled` boolean — A boolean flag to enable CDN caching.
      - `region_priorities` object — A map of region string to an integer priority value indicating preference for which regional target a Global load balancer will forward traffic to. A lower value indicates a higher priority.
      - `failover_threshold` integer — An integer value as a percentage to indicate failure threshold to decide how the regional priorities will take effect. A value of `50` would indicate that the Global load balancer will choose a lower priority region to forward traffic to once this failure threshold has been reached for the higher priority region.
    - `target_load_balancer_ids` string[] — An array containing the UUIDs of the Regional load balancers to be used as target backends for a Global load balancer.
    - `tls_cipher_policy` 'DEFAULT' | 'STRONG' — A string indicating the policy for the TLS cipher suites used by the load balancer. The possible values are `DEFAULT` or `STRONG`. The default value is `DEFAULT`.
  - object
    - `tag` string, required — The name of a Droplet tag corresponding to Droplets assigned to the load balancer.
    - `region` 'ams1' | 'ams2' | 'ams3' | 'blr1' | 'fra1' | 'lon1' | 'nyc1' | 'nyc2' | 'nyc3' | 'sfo1' | 'sfo2' | 'sfo3' | 'sgp1' | 'tor1' | 'syd1', required — The slug identifier for the region where the resource will initially be available.
    - `id` string, uuid — A unique ID that can be used to identify and reference a load balancer.
    - `name` string — A human-readable name for a load balancer instance.
    - `project_id` string — The ID of the project that the load balancer is associated with. If no ID is provided at creation, the load balancer associates with the user's default project. If an invalid project ID is provided, the load balancer will not be created.
    - `ip` string — An attribute containing the public-facing IP address of the load balancer.
    - `ipv6` string — An attribute containing the public-facing IPv6 address of the load balancer.
    - `size_unit` integer — How many nodes the load balancer contains. Each additional node increases the load balancer's ability to manage more connections. Load balancers can be scaled up or down, and you can change the number of nodes after creation up to once per hour. This field is currently not available in the AMS2, NYC2, or SFO1 regions. Use the `size` field to scale load balancers that reside in these regions.
    - `size` 'lb-small' | 'lb-medium' | 'lb-large' — This field has been replaced by the `size_unit` field for all regions except in AMS2, NYC2, and SFO1. Each available load balancer size now equates to the load balancer having a set number of nodes. * `lb-small` = 1 node * `lb-medium` = 3 nodes * `lb-large` = 6 nodes You can resize load balancers after creation up to once per hour. You cannot resize a load balancer within the first hour of its creation.
    - `algorithm` 'round_robin' | 'least_connections' — This field has been deprecated. You can no longer specify an algorithm for load balancers.
    - `status` 'new' | 'active' | 'errored' — A status string indicating the current state of the load balancer. This can be `new`, `active`, or `errored`.
    - `created_at` string, date-time — A time value given in ISO8601 combined date and time format that represents when the load balancer was created.
    - `forwarding_rules` ForwardingRule[], required — An array of objects specifying the forwarding rules for a load balancer.
      - `entry_protocol` 'http' | 'https' | 'http2' | 'http3' | 'tcp' | 'udp', required — The protocol used for traffic to the load balancer. The possible values are: `http`, `https`, `http2`, `http3`, `tcp`, or `udp`. If you set the `entry_protocol` to `udp`, the `target_protocol` must be set to `udp`. When using UDP, the load balancer requires that you set up a health check with a port that uses TCP, HTTP, or HTTPS to work properly.
      - `entry_port` integer, required — An integer representing the port on which the load balancer instance will listen.
      - `target_protocol` 'http' | 'https' | 'http2' | 'tcp' | 'udp', required — The protocol used for traffic from the load balancer to the backend Droplets. The possible values are: `http`, `https`, `http2`, `tcp`, or `udp`. If you set the `target_protocol` to `udp`, the `entry_protocol` must be set to `udp`. When using UDP, the load balancer requires that you set up a health check with a port that uses TCP, HTTP, or HTTPS to work properly.
      - `target_port` integer, required — An integer representing the port on the backend Droplets to which the load balancer will send traffic.
      - `certificate_id` string — The ID of the TLS certificate used for SSL termination if enabled.
      - `tls_passthrough` boolean — A boolean value indicating whether SSL encrypted traffic will be passed through to the backend Droplets.
    - `health_check` HealthCheck — An object specifying health check settings for the load balancer.
      - `protocol` 'http' | 'https' | 'tcp' — The protocol used for health checks sent to the backend Droplets. The possible values are `http`, `https`, or `tcp`.
      - `port` integer — An integer representing the port on the backend Droplets on which the health check will attempt a connection.
      - `path` string — The path on the backend Droplets to which the load balancer instance will send a request.
      - `check_interval_seconds` integer — The number of seconds between between two consecutive health checks.
      - `response_timeout_seconds` integer — The number of seconds the load balancer instance will wait for a response until marking a health check as failed.
      - `unhealthy_threshold` integer — The number of times a health check must fail for a backend Droplet to be marked "unhealthy" and be removed from the pool.
      - `healthy_threshold` integer — The number of times a health check must pass for a backend Droplet to be marked "healthy" and be re-added to the pool.
    - `sticky_sessions` StickySessions — An object specifying sticky sessions settings for the load balancer.
      - `type` 'cookies' | 'none' — An attribute indicating how and if requests from a client will be persistently served by the same backend Droplet. The possible values are `cookies` or `none`.
      - `cookie_name` string — The name of the cookie sent to the client. This attribute is only returned when using `cookies` for the sticky sessions type.
      - `cookie_ttl_seconds` integer — The number of seconds until the cookie set by the load balancer expires. This attribute is only returned when using `cookies` for the sticky sessions type.
    - `redirect_http_to_https` boolean — A boolean value indicating whether HTTP requests to the load balancer on port 80 will be redirected to HTTPS on port 443.
    - `enable_proxy_protocol` boolean — A boolean value indicating whether PROXY Protocol is in use.
    - `enable_backend_keepalive` boolean — A boolean value indicating whether HTTP keepalive connections are maintained to target Droplets.
    - `http_idle_timeout_seconds` integer — An integer value which configures the idle timeout for HTTP requests to the target droplets.
    - `vpc_uuid` string, uuid — A string specifying the UUID of the VPC to which the load balancer is assigned.
    - `disable_lets_encrypt_dns_records` boolean — A boolean value indicating whether to disable automatic DNS record creation for Let's Encrypt certificates that are added to the load balancer.
    - `firewall` LbFirewall — An object specifying allow and deny rules to control traffic to the load balancer.
      - `deny` string[] — the rules for denying traffic to the load balancer (in the form 'ip:1.2.3.4' or 'cidr:1.2.0.0/16')
      - `allow` string[] — the rules for allowing traffic to the load balancer (in the form 'ip:1.2.3.4' or 'cidr:1.2.0.0/16')
    - `network` 'EXTERNAL' | 'INTERNAL' — A string indicating whether the load balancer should be external or internal. Internal load balancers have no public IPs and are only accessible to resources on the same VPC network. This property cannot be updated after creating the load balancer.
    - `network_stack` 'IPV4' | 'DUALSTACK' — A string indicating whether the load balancer will support IPv4 or both IPv4 and IPv6 networking. This property cannot be updated after creating the load balancer.
    - `type` 'REGIONAL' | 'REGIONAL_NETWORK' | 'GLOBAL' — A string indicating whether the load balancer should be a standard regional HTTP load balancer, a regional network load balancer that routes traffic at the TCP/UDP transport layer, or a global load balancer.
    - `domains` Domains[] — An array of objects specifying the domain configurations for a Global load balancer.
      - `name` string — FQDN to associate with a Global load balancer.
      - `is_managed` boolean — A boolean value indicating if the domain is already managed by DigitalOcean. If true, all A and AAAA records required to enable Global load balancers will be automatically added.
      - `certificate_id` string — The ID of the TLS certificate used for SSL termination.
    - `glb_settings` GlbSettings — An object specifying forwarding configurations for a Global load balancer.
      - `target_protocol` 'http' | 'https' | 'http2' — The protocol used for forwarding traffic from the load balancer to the target backends. The possible values are `http`, `https` and `http2`.
      - `target_port` integer — An integer representing the port on the target backends which the load balancer will forward traffic to.
      - `cdn` object — An object specifying CDN configurations for a Global load balancer.
        - `is_enabled` boolean — A boolean flag to enable CDN caching.
      - `region_priorities` object — A map of region string to an integer priority value indicating preference for which regional target a Global load balancer will forward traffic to. A lower value indicates a higher priority.
      - `failover_threshold` integer — An integer value as a percentage to indicate failure threshold to decide how the regional priorities will take effect. A value of `50` would indicate that the Global load balancer will choose a lower priority region to forward traffic to once this failure threshold has been reached for the higher priority region.
    - `target_load_balancer_ids` string[] — An array containing the UUIDs of the Regional load balancers to be used as target backends for a Global load balancer.
    - `tls_cipher_policy` 'DEFAULT' | 'STRONG' — A string indicating the policy for the TLS cipher suites used by the load balancer. The possible values are `DEFAULT` or `STRONG`. The default value is `DEFAULT`.

## Response `202`

Accepted

- object
  - `load_balancer` LoadBalancer
    - `id` string, uuid — A unique ID that can be used to identify and reference a load balancer.
    - `name` string — A human-readable name for a load balancer instance.
    - `project_id` string — The ID of the project that the load balancer is associated with. If no ID is provided at creation, the load balancer associates with the user's default project. If an invalid project ID is provided, the load balancer will not be created.
    - `ip` string — An attribute containing the public-facing IP address of the load balancer.
    - `ipv6` string — An attribute containing the public-facing IPv6 address of the load balancer.
    - `size_unit` integer — How many nodes the load balancer contains. Each additional node increases the load balancer's ability to manage more connections. Load balancers can be scaled up or down, and you can change the number of nodes after creation up to once per hour. This field is currently not available in the AMS2, NYC2, or SFO1 regions. Use the `size` field to scale load balancers that reside in these regions.
    - `size` 'lb-small' | 'lb-medium' | 'lb-large' — This field has been replaced by the `size_unit` field for all regions except in AMS2, NYC2, and SFO1. Each available load balancer size now equates to the load balancer having a set number of nodes. * `lb-small` = 1 node * `lb-medium` = 3 nodes * `lb-large` = 6 nodes You can resize load balancers after creation up to once per hour. You cannot resize a load balancer within the first hour of its creation.
    - `algorithm` 'round_robin' | 'least_connections' — This field has been deprecated. You can no longer specify an algorithm for load balancers.
    - `status` 'new' | 'active' | 'errored' — A status string indicating the current state of the load balancer. This can be `new`, `active`, or `errored`.
    - `created_at` string, date-time — A time value given in ISO8601 combined date and time format that represents when the load balancer was created.
    - `forwarding_rules` ForwardingRule[], required — An array of objects specifying the forwarding rules for a load balancer.
      - `entry_protocol` 'http' | 'https' | 'http2' | 'http3' | 'tcp' | 'udp', required — The protocol used for traffic to the load balancer. The possible values are: `http`, `https`, `http2`, `http3`, `tcp`, or `udp`. If you set the `entry_protocol` to `udp`, the `target_protocol` must be set to `udp`. When using UDP, the load balancer requires that you set up a health check with a port that uses TCP, HTTP, or HTTPS to work properly.
      - `entry_port` integer, required — An integer representing the port on which the load balancer instance will listen.
      - `target_protocol` 'http' | 'https' | 'http2' | 'tcp' | 'udp', required — The protocol used for traffic from the load balancer to the backend Droplets. The possible values are: `http`, `https`, `http2`, `tcp`, or `udp`. If you set the `target_protocol` to `udp`, the `entry_protocol` must be set to `udp`. When using UDP, the load balancer requires that you set up a health check with a port that uses TCP, HTTP, or HTTPS to work properly.
      - `target_port` integer, required — An integer representing the port on the backend Droplets to which the load balancer will send traffic.
      - `certificate_id` string — The ID of the TLS certificate used for SSL termination if enabled.
      - `tls_passthrough` boolean — A boolean value indicating whether SSL encrypted traffic will be passed through to the backend Droplets.
    - `health_check` HealthCheck — An object specifying health check settings for the load balancer.
      - `protocol` 'http' | 'https' | 'tcp' — The protocol used for health checks sent to the backend Droplets. The possible values are `http`, `https`, or `tcp`.
      - `port` integer — An integer representing the port on the backend Droplets on which the health check will attempt a connection.
      - `path` string — The path on the backend Droplets to which the load balancer instance will send a request.
      - `check_interval_seconds` integer — The number of seconds between between two consecutive health checks.
      - `response_timeout_seconds` integer — The number of seconds the load balancer instance will wait for a response until marking a health check as failed.
      - `unhealthy_threshold` integer — The number of times a health check must fail for a backend Droplet to be marked "unhealthy" and be removed from the pool.
      - `healthy_threshold` integer — The number of times a health check must pass for a backend Droplet to be marked "healthy" and be re-added to the pool.
    - `sticky_sessions` StickySessions — An object specifying sticky sessions settings for the load balancer.
      - `type` 'cookies' | 'none' — An attribute indicating how and if requests from a client will be persistently served by the same backend Droplet. The possible values are `cookies` or `none`.
      - `cookie_name` string — The name of the cookie sent to the client. This attribute is only returned when using `cookies` for the sticky sessions type.
      - `cookie_ttl_seconds` integer — The number of seconds until the cookie set by the load balancer expires. This attribute is only returned when using `cookies` for the sticky sessions type.
    - `redirect_http_to_https` boolean — A boolean value indicating whether HTTP requests to the load balancer on port 80 will be redirected to HTTPS on port 443.
    - `enable_proxy_protocol` boolean — A boolean value indicating whether PROXY Protocol is in use.
    - `enable_backend_keepalive` boolean — A boolean value indicating whether HTTP keepalive connections are maintained to target Droplets.
    - `http_idle_timeout_seconds` integer — An integer value which configures the idle timeout for HTTP requests to the target droplets.
    - `vpc_uuid` string, uuid — A string specifying the UUID of the VPC to which the load balancer is assigned.
    - `disable_lets_encrypt_dns_records` boolean — A boolean value indicating whether to disable automatic DNS record creation for Let's Encrypt certificates that are added to the load balancer.
    - `firewall` LbFirewall — An object specifying allow and deny rules to control traffic to the load balancer.
      - `deny` string[] — the rules for denying traffic to the load balancer (in the form 'ip:1.2.3.4' or 'cidr:1.2.0.0/16')
      - `allow` string[] — the rules for allowing traffic to the load balancer (in the form 'ip:1.2.3.4' or 'cidr:1.2.0.0/16')
    - `network` 'EXTERNAL' | 'INTERNAL' — A string indicating whether the load balancer should be external or internal. Internal load balancers have no public IPs and are only accessible to resources on the same VPC network. This property cannot be updated after creating the load balancer.
    - `network_stack` 'IPV4' | 'DUALSTACK' — A string indicating whether the load balancer will support IPv4 or both IPv4 and IPv6 networking. This property cannot be updated after creating the load balancer.
    - `type` 'REGIONAL' | 'REGIONAL_NETWORK' | 'GLOBAL' — A string indicating whether the load balancer should be a standard regional HTTP load balancer, a regional network load balancer that routes traffic at the TCP/UDP transport layer, or a global load balancer.
    - `domains` Domains[] — An array of objects specifying the domain configurations for a Global load balancer.
      - `name` string — FQDN to associate with a Global load balancer.
      - `is_managed` boolean — A boolean value indicating if the domain is already managed by DigitalOcean. If true, all A and AAAA records required to enable Global load balancers will be automatically added.
      - `certificate_id` string — The ID of the TLS certificate used for SSL termination.
    - `glb_settings` GlbSettings — An object specifying forwarding configurations for a Global load balancer.
      - `target_protocol` 'http' | 'https' | 'http2' — The protocol used for forwarding traffic from the load balancer to the target backends. The possible values are `http`, `https` and `http2`.
      - `target_port` integer — An integer representing the port on the target backends which the load balancer will forward traffic to.
      - `cdn` object — An object specifying CDN configurations for a Global load balancer.
        - `is_enabled` boolean — A boolean flag to enable CDN caching.
      - `region_priorities` object — A map of region string to an integer priority value indicating preference for which regional target a Global load balancer will forward traffic to. A lower value indicates a higher priority.
      - `failover_threshold` integer — An integer value as a percentage to indicate failure threshold to decide how the regional priorities will take effect. A value of `50` would indicate that the Global load balancer will choose a lower priority region to forward traffic to once this failure threshold has been reached for the higher priority region.
    - `target_load_balancer_ids` string[] — An array containing the UUIDs of the Regional load balancers to be used as target backends for a Global load balancer.
    - `tls_cipher_policy` 'DEFAULT' | 'STRONG' — A string indicating the policy for the TLS cipher suites used by the load balancer. The possible values are `DEFAULT` or `STRONG`. The default value is `DEFAULT`.
    - `region` object — The region where the load balancer instance is located. When setting a region, the value should be the slug identifier for the region. When you query a load balancer, an entire region object will be returned.
      - `name` string, required — The display name of the region. This will be a full name that is used in the control panel and other interfaces.
      - `slug` string, required — A human-readable string that is used as a unique identifier for each region.
      - `features` string[], required — This attribute is set to an array which contains features available in this region
      - `available` boolean, required — This is a boolean value that represents whether new Droplets can be created in this region.
      - `sizes` string[], required — This attribute is set to an array which contains the identifying slugs for the sizes available in this region. sizes:read is required to view.
    - `droplet_ids` integer[] — An array containing the IDs of the Droplets assigned to the load balancer.
    - `tag` string — The name of a Droplet tag corresponding to Droplets assigned to the load balancer.

## Other responses

- `401` — Authentication failed due to invalid credentials.
- `429` — The API rate limit has been exceeded.
- `500` — There was a server error.
- `default` — There was an unexpected error.

---

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