tencent cloud

CloudAudit

Product Introduction
Overview
Strengths
Features
Scenarios
CloudAudit-Enabled Services and APIs
Purchase Guide
Getting Started
Operation Guide
Viewing Event Details in Operation Record
Shipping Log with Tracking Set
Set up cross-account log delivery for group accounts
Sensitive Operation API List
API Documentation
History
Introduction
API Category
Calling Method
CloudAudit APIs
Data Types
Error Codes
PHP SDK Documentation
Creating CloudAudit
Enabling Log Collection
Updating CloudAudit
Disabling Log Collection
Fetching Bucket List of COS
Fetching CloudAudit List
Obtaining CloudAudit Info
Deleting CloudAudit
Searching Operation Logs
FAQs
Contact Us
Glossary
DocumentationCloudAuditAPI DocumentationCalling MethodRequest Structure

Request Structure

PDF
Focus Mode
Font Size
Last updated: 2025-10-30 21:35:55

1. Service Address

The API supports access from either a nearby region (at cloudaudit.intl.tencentcloudapi.com) or a specified region (at cloudaudit.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 "cloudaudit.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) cloudaudit.intl.tencentcloudapi.com
South China (Guangzhou) cloudaudit.ap-guangzhou.tencentcloudapi.com
East China (Shanghai) cloudaudit.ap-shanghai.tencentcloudapi.com
East China (Nanjing) cloudaudit.ap-nanjing.tencentcloudapi.com
North China (Beijing) cloudaudit.ap-beijing.tencentcloudapi.com
Southwest China (Chengdu) cloudaudit.ap-chengdu.tencentcloudapi.com
Southwest China (Chongqing) cloudaudit.ap-chongqing.tencentcloudapi.com
Hong Kong, Macao, Taiwan (Hong Kong, China) cloudaudit.ap-hongkong.tencentcloudapi.com
Southeast Asia (Singapore) cloudaudit.ap-singapore.tencentcloudapi.com
Southeast Asia (Jakarta) cloudaudit.ap-jakarta.tencentcloudapi.com
Southeast Asia (Bangkok) cloudaudit.ap-bangkok.tencentcloudapi.com
Northeast Asia (Seoul) cloudaudit.ap-seoul.tencentcloudapi.com
Northeast Asia (Tokyo) cloudaudit.ap-tokyo.tencentcloudapi.com
U.S. East Coast (Virginia) cloudaudit.na-ashburn.tencentcloudapi.com
U.S. West Coast (Silicon Valley) cloudaudit.na-siliconvalley.tencentcloudapi.com
South America (São Paulo) cloudaudit.sa-saopaulo.tencentcloudapi.com
Europe (Frankfurt) cloudaudit.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.

Previous Topic: API CategoryNext Topic: Common Params

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback