tencent cloud

Anti-DDoS

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Overview
Strengths
Use Cases
Concepts
Blocking Policies
Relevant Products
Comparison of Anti-DDoS Solutions
Purchase Guide
Billing Overview
Purchase Directions
Getting Started
Anti-DDoS Pro
Anti-DDoS Advanced
Operation Guide
Operation Overview
Protection Overview
Usage Limits
Asset Center
Business Connection
Smart Scheduling
Protection Configuration
Security Operations
Service Management
Practical Tutorial
Remote Protection Scheme with Anti-DDoS Pro
Using Anti-DDoS Pro Together with WFA
Suggestions on Stress Tests
Solutions to Real Server IP Exposure
Creating an Anti-DDoS EIP
Configuration Directions and Notes on CC Protection Policies
Syncing Forwarding Rules to New Anti-DDoS Advanced Instances
‌Smart Scheduling of CTCC/CUCC/CMCC Traffic
Troubleshooting
Business IPs Blocked Due to High-traffic Attacks
‌Business IPs Blocked When DDoS Attack Traffic Doesn't Reach the Threshold
How to Fix a 502 Bad Gateway Error
"No ICP filing" Prompted During Domain Name Connection
A public IP suffered DDoS attacks
API Documentation
History
Introduction
API Category
Making API Requests
Anti-DDoS Advanced Instance APIs
Resource List APIs
Protection Configuration APIs
Other APIs
Alarm Notification APIs
Connection Configuration APIs
Intelligent Scheduling APIs
Black hole unblocking APIs
Statistical Report APIs
Data Types
Error Codes
FAQs
Blocking
Attacks
Features
Billing
Service Level Agreement
Product Policy
Privacy Policy
Data Processing And Security Agreement
Glossary

Request Structure

PDF
Focus Mode
Font Size
Last updated: 2025-10-30 21:26:27

1. Service Address

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

Help and Support

Was this page helpful?

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

Feedback