tencent cloud

Tencent Cloud Super App as a Service

Release Notes and Announcements
Announcement: Tencent Cloud Mini Program Platform Renamed to Tencent Cloud Super App as a Service on January 2, 2025
Console Updates
Android SDK Updates
iOS SDK Updates
Flutter SDK Updates
IDE Updates
Base Library Updates
Product Introduction
Overview
Strengths
Use Cases
Purchase Guide
Billing Overview
Pay-As-You-Go Billing
Renewal Guide
Service Suspension Instructions
Getting Started
Plan Management
Overview
Console Account Management
Storage Configuration
Acceleration Configuration
Branding Configurations
Platform Features
Console Login
Users and Permission System
Mini Program Management
Mini Game Management
Superapp Management
Commercialization
Platform Management
User Management
Team Management
Operations Management
Security Center
Code Integration Guide
Getting Demo and SDK
Android
iOS
Flutter
Superapp Server
GUID Generation Rules
Mini Program Development Guide
Mini Program Introduction and Development Environment
Mini Program Code Composition
Guide
Framework
Components
API
Server Backend
JS SDK
Base Library
IDE Operation Instructions
Mini Game Development Guide
Guide
API
Server Backend
Practice Tutorial
Mini Program Login Practical Tutorial
Mini Program Subscription Message Practical Tutorial
Payment Practical Tutorial
Ad Integration Practical Tutorial
Mini Game Subscription Message Practical Tutorial
API Documentation
History
Introduction
API Category
Making API Requests
Operation Management APIs
User Management APIs
Team Management APIs
Sensitive API-Related APIs
Role Management APIs
Platform Management APIs
Other Console APIs
Mini Program or Mini Game APIs
Management-Sensitive APIs
Global Domain Management APIs
Superapp APIs
Data Types
Agreements
Service Level Agreement
Data Processing and Security Agreement
SDK Privacy Policy Module
SDK Data Processing and Security Agreement Module

Request Structure

PDF
Focus Mode
Font Size
Last updated: 2026-03-17 11:25:55

1. Service Address

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