tencent cloud

Tencent Cloud Lighthouse

Release Notes and Announcements
Image Release Notes
Announcements
Product Introduction
Overview
Basic Concepts
Strengths
Scenarios
Use Limits
Region and Network Connectivity
Product Comparison
User Guide
Billing
Billing Overview
Instance Package
Pricing Details
Purchase Methods
Configuration Adjustment (for Upgrade Only)
Overdue Payments
Refund
Getting Started
One-Click Application Creation Using Lighthouse
Quick Instance Creation
User Guide
Instances
Cloud Disks
Images
Firewall
Private Network Interconnection
Data Backup and Restoration Using Snapshots
Cloud Access Management
OPS and Monitoring
File Transfer
Use Cases
Website Building
Development Environment Building
Cloud Storage System Building
E-commerce Platform Building
Personal Live Streaming Room Building
FTP Service Building
SSL Certificate Installation
Troubleshooting
Windows Instance: RDP Connection to the Remote Computer Fails
Windows Instance: Offline Password Resetting Fails or Invalid
Linux/Windows Instance: Online Password Resetting Fails or Invalid
API Documentation
History
Introduction
API Category
Making API Requests
Image APIs
Firewall APIs
Key APIs
Instance APIs
Snapshot APIs
CCN APIs
Other APIs
Cloud Disk APIs
Scene APIs
Package APIs
Quota APIs
Region APIs
Data Types
Error Codes
FAQs
Agreements
Privacy Policy
Data Processing And Security Agreement
Contact Us

Request Structure

PDF
フォーカスモード
フォントサイズ
最終更新日: 2026-03-06 14:44:30

1. Service Address

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

ヘルプとサポート

この記事はお役に立ちましたか?

フィードバック