tencent cloud

Tencent Cloud TCHouse-D

Product Introduction
Overview
Concepts
Cluster Architecture
Strengths
Scenarios
Purchase Guide
Billing Overview
Renewal Instructions
Overdue Policy
Refund Instructions
Configuration Adjustment Billing Instructions
Getting Started
Using Tencent Cloud TCHouse-D Through the Console
Using Tencent Cloud TCHouse-D Through a Client
Operation Guide
Cluster Operation
Monitoring and Alarm Configuration
Account Privilege Management
Data Management
Query Management
Modify Configurations
Node Management
Log Analysis
SQL Studio
Enabling Resource Isolation
Development Guide
Design of Data Table
Importing Data
Exporting Data
Basic Feature
Query Optimization
Ecological Expansion Feature
API Documentation
History
Introduction
API Category
Making API Requests
Cluster Operation APIs
Database and Table APIs
Cluster Information Viewing APIs
Hot-Cold Data Layering APIs
Database and Operation Audit APIs
User and Permission APIs
Resource Group Management APIs
Data Types
Error Codes
Cloud Ecosystem
Granting CAM Policies to Sub-accounts
Query Acceleration for Tencent Cloud DLC
Practical Tutorial
Basic Feature Usage
Advanced Features Usage
Resource Specification Selection and Optimization Suggestions
Naming Specifications and Limits to the Database and Data Table
Table Design and Data Import
Query Optimization
Suggested Usage to Avoid
Accessing TCHouse-D via JDBC over the Public Network
Performance Testing
TPC-H Performance Testing
SSB Performance Testing
TPC-DS Performance Testing
FAQs
Common Operational Issues
Common Errors
Contact Us
Glossary
Product Policy
Service Level Agreement
Privacy Policy
Data Processing And Security Agreement
ドキュメントTencent Cloud TCHouse-DAPI DocumentationMaking API RequestsRequest Structure

Request Structure

PDF
フォーカスモード
フォントサイズ
最終更新日: 2025-10-30 21:32:01

1. Service Address

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

前の記事へ: API Category次の記事へ: Common Params

ヘルプとサポート

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

フィードバック