tencent cloud

Cloud Block Storage

User Guide
Announcements
Announcement of the Commercial Charges of Tencent Cloud CBS Snapshot
Announcement of the Commercial Charges of Tencent Cloud CBS Snapshot Cross-Region Replication
Product Introduction
Overview
Strengths
Scenarios
Regions and AZs
Cloud Disk Instances
Cloud Disk Snapshots
Access Management
Related Products
Predecessor
Service Regions and Service Providers
Billing
Billing Overview
Price Overview
Purchase Instructions
Renewal Guide
Overdue Payment
Getting Started
Step 1. Creating Cloud Disks
Step 2. Attaching Cloud Disks
Step 3. Initializing Cloud Disks
User Guide
Operation Overview
Usage Limits
Creating Cloud Disks
Attaching Cloud Disks
Initializing Cloud Disks
Expanding Cloud Disks
Detaching Cloud Disks
Terminating Cloud Disks
Viewing Cloud Disk Information
Adjusting Cloud Disk Types
Adjusting Cloud Disk Performance
Cloud Disk Data Protection Configuration
Cloud Disk Data Backup Point
Managing Snapshots
Monitoring and Alarms
Use Cases
Measuring Cloud Disk Performance
Building LVM Logic Volumes with Multiple Elastic Cloud Disks
Expanding MBR Cloud Disks to Greater Than 2 TB
Troubleshooting
Failed to Unmount Cloud Disks from Windows CVM Instances
Disk Not Mount upon Linux CVM Restart
API Documentation
History
Introduction
API Category
Making API Requests
Snapshot APIs
Cloud Disk APIs
Data Types
Error Codes
FAQs
Features
Billing
Performance FAQs
Snapshot
Usage
Cross-region Replication
CBS Service Level Agreement
Contact Us
Glossary

Request Structure

PDF
フォーカスモード
フォントサイズ
最終更新日: 2026-02-27 17:45:48

1. Service Address

The API supports access from either a nearby region (at cbs.intl.tencentcloudapi.com) or a specified region (at cbs.ap-guangzhou.tencentcloudapi.com for Guangzhou, for example).

We recommend using the domain name to access the nearest server. When you call an API, the request is automatically resolved to a server in the region nearest to the location where the API is initiated. For example, when you initiate an API request in Guangzhou, this domain name is automatically resolved to a Guangzhou server, the result is the same as that of specifying the region in the domain like "cbs.ap-guangzhou.tencentcloudapi.com".

Note: For latency-sensitive businesses, we recommend that you specify the region in the domain name.

Tencent Cloud currently supports the following regions:

Hosted region Domain name
Local access region (recommended, only for non-financial availability zones) cbs.intl.tencentcloudapi.com
South China (Guangzhou) cbs.ap-guangzhou.tencentcloudapi.com
East China (Shanghai) cbs.ap-shanghai.tencentcloudapi.com
East China (Nanjing) cbs.ap-nanjing.tencentcloudapi.com
North China (Beijing) cbs.ap-beijing.tencentcloudapi.com
Southwest China (Chengdu) cbs.ap-chengdu.tencentcloudapi.com
Southwest China (Chongqing) cbs.ap-chongqing.tencentcloudapi.com
Hong Kong, Macao, Taiwan (Hong Kong, China) cbs.ap-hongkong.tencentcloudapi.com
Southeast Asia (Singapore) cbs.ap-singapore.tencentcloudapi.com
Southeast Asia (Jakarta) cbs.ap-jakarta.tencentcloudapi.com
Southeast Asia (Bangkok) cbs.ap-bangkok.tencentcloudapi.com
Northeast Asia (Seoul) cbs.ap-seoul.tencentcloudapi.com
Northeast Asia (Tokyo) cbs.ap-tokyo.tencentcloudapi.com
U.S. East Coast (Virginia) cbs.na-ashburn.tencentcloudapi.com
U.S. West Coast (Silicon Valley) cbs.na-siliconvalley.tencentcloudapi.com
South America (São Paulo) cbs.sa-saopaulo.tencentcloudapi.com
Europe (Frankfurt) cbs.eu-frankfurt.tencentcloudapi.com

2. Communications Protocol

All the Tencent Cloud APIs communicate via HTTPS, providing highly secure communication tunnels.

3. Request Methods

Supported HTTP request methods:

  • POST (recommended)
  • GET

The Content-Type types supported by POST requests:

  • application/json (recommended). The TC3-HMAC-SHA256 signature algorithm must be used.
  • application/x-www-form-urlencoded. The HmacSHA1 or HmacSHA256 signature algorithm must be used.
  • multipart/form-data (only supported by certain APIs). You must use TC3-HMAC-SHA256 to calculate the signature.

The size of a GET request packet is up to 32 KB. The size of a POST request is up to 1 MB when the HmacSHA1 or HmacSHA256 signature algorithm is used, and up to 10 MB when TC3-HMAC-SHA256 is used.

4. Character Encoding

Only UTF-8 encoding is used.

ヘルプとサポート

この記事はお役に立ちましたか?

フィードバック