tencent cloud

Tencent Cloud Elastic Microservice

Release Notes and Announcements
Announcements
Release Notes
Product Introduction
Overview
Strengths
Scenarios
Purchase Guide
Billing Overview
Product Pricing
Overdue Policies
Getting Started
Step 1. Get the Access Permission
Step 2. Create an Environment
Step 3. Create an Application
Step 4. Deploy the Application
Operation Guide
Environment Management
Application Management
Permission Management
View Change Record
Practical Tutorial
Use of GitHub Actions in TEM
Hosting a Static Website
Public Network Access of TEM Applications
TEM Application Access to Public Network (Through API Gateway)
TEM Application Failure Troubleshooting Guide
Quick Access to TEM Application Through API Gateway
Java Application Fine-Tuning
Migration from Java 8 to Java 11
API Documentation
History
Introduction
API Category
Making API Requests
Environment APIs
ModifyIngress
Resource APIs
Application APIs
Service APIs
RollingUpdateApplicationByVersion
Access Policy APIs
Configuration file APIs
Log collecting APIs
Scaling Rule APIs
Application Version APIs
Other APIs
Workload APIs
Data Types
Error Codes
FAQs
TEM Configuration
Contact Us
Glossary
TEM Policy
Privacy Policy
Data Privacy and Security Agreement

Request Structure

PDF
Focus Mode
Font Size
Last updated: 2025-11-13 21:12:55

1. Service Address

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