tencent cloud

Tencent Container Security Service

Release Notes
Product Introduction
Overview
Strengths
Use Cases
Features and Versions
Purchase Guide
Applying for Trial
Purchasing Pro Edition
Purchasing Image Scan
Purchasing Log Analysis
Getting Started
Operation Guide
Security Overview
Asset Management
Vulnerability Detection
Image Risk Management
Cluster Risk Management
Baseline Management
Runtime Security
Advanced Defense
Policy Management
Protection Switch
Alarm Settings
Log Analysis
Hybrid Cloud Installation Guide
Compromised Container Isolation
Log Field Data Parsing
Practical Tutorial
Mirror Vulnerability Scanning and Vulnerability Management
Troubleshooting
Offline Linux Client
Troubleshooting for Cluster Access
API Documentation
History
Introduction
API Category
Making API Requests
Network Security APIs
Cluster Security APIs
Security Compliance APIs
Runtime security - High-risk syscalls
Runtime Security - Reverse Shell APIs
Runtime Security APIs
Alert Settings APIs
Advanced prevention - K8s API abnormal requests
Asset Management APIs
Security Operations - Log Analysis APIs
Runtime Security - Trojan Call APIs
Runtime Security - Container Escape APIs
Image Security APIs
Billing APIs
Data Types
Error Codes
FAQs
TCSS Policy
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary
DocumentationTencent Container Security ServiceAPI DocumentationMaking API RequestsRequest Structure

Request Structure

PDF
Focus Mode
Font Size
Last updated: 2025-10-30 21:59:20

1. Service Address

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