Docs

Load Balancer

API reference

Overview

Welcome to Classic Load Balancer (CLB). This document provides descriptions, syntax, parameters, and examples of CLB APIs. You can call these APIs to manage your cloud resources.

Calls to some CLB APIs may fail due to subaccount permission limits. In such cases, contact the primary account to obtain permissions. For more information, refer to Permission management.

You can call relevant APIs using the Software Development Kit (SDK). For more information, refer to SDK overview.

Concepts

Name	Description
Regions	The internal networks of different Regions are isolated. A Region closer to your business is recommended because the network latency can be kept low, and access speed can be faster.
AZ	An availability zone is a physical area with an isolated power grid and network in a region. Internal networks of different Availability Zones in the same Virtual Private Cloud (VPC) are interconnected. It is recommended to deploy instances with low-latency requirements in the same Availability Zone, and instances with disaster recovery needs in different Availability Zones in the same Region.
Root user	An account, or a primary account, is an entity within BytePlus for which resources are allocated, measured, and billed. Before you use BytePlus services, you must sign up for a BytePlus account. The username of the account is usually used as the login identifier of it. An account is the owner of all the service resources under itself. It has full access to all the resources. You can use it to purchase, renew, unsubscribe, and upgrade those resources. It also owns the purchase orders and bills of those resources. Service resources can be accessed and manipulated by accounts they belong to.
Subaccount	A subaccount, or an Identity and Access Management (IAM) account, is an authorized entity of the primary account and also a resource belonging to the primary account. An IAM user does not own any service resources and is not independently billed. An IAM user is only authorized by the primary account to manage the resources of the primary account. Resources managed by an IAM user are owned and paid for by the primary account. When an authorized IAM user is granted a password and an AccessKey, the user can log on to the console and use open APIs to manage the resources of the primary account.

Last updated: 2025.09.26 16:51:26