tencent cloud

Content Delivery Network

Updates and Announcements
Release Notes
Announcements
User Tutorial
Product Introduction
Product Overview
Strengths
Use Cases
Term
Use Limits
CDN Performance Descriptions (Spot-check)
Purchase Guide
CDN Purchase Guide
ECDN Purchase Guide
Getting Started
Configuring CDN from Scratch
Adding Domain Names
CNAME Configuration
Domain Name Ownership Verification
FAQs about Domain Name Connection
Configuration Guide
Domain Management
Domain Name Configurations
Statistical Analysis
Purge and Prefetch
Log Management
EdgeOne
Service Query
Offline Cache
Permission Management
Permission Configuration
Console Permissions
Activate Real-time Logging as Sub-account/Collaborator
Use Cases
Accelerating Resources on COS with CDN
Practical Tutorial
Guide to Using the EdgeOne Tool for Migrating Content Delivery Network (CDN) Related Services
CDN - CVM
CDN - COS
Configuring CNAME via DNSPod
Regularly Storing CDN Logs
API Documentation
History
Introduction
API Category
Content Management APIs
Real-time Log APIs
Service Query APIs
Data Query APIs
Making API Requests
Log Query APIs
StopCdnDomain
Configuration Management APIs
Obsoleted APIs
Other APIs
Data Types
Error Codes
FAQ
Features
Billing
FAQs about Domain Name Connection
Cache Configuration FAQs
Purge and Prefetch
Statistical Analysis
FAQs about HTTPS
Connection
Errors
Troubleshooting Methods
Status Codes and Solutions
Node Cache Inconsistency
Slow Access Speed After CDN Activation
Low Traffic Hit Rate
404 Status Code
Page Display - CORS error
Resource Cache Failure
Service Level Agreement
Glossary
DocumentationContent Delivery NetworkAPI Documentation Making API RequestsRequest Structure

Request Structure

PDF
Focus Mode
Font Size
Last updated: 2025-12-24 10:38:40

1. Service Address

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

Help and Support

Was this page helpful?

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

Feedback