tencent cloud

Tencent Cloud WeData

Release Notes
Dynamic Release Record (2026)
Product Introduction
Product Overview
Product Advantages
Product Architecture
Product Features
Application Scenarios
Purchase Guide
Billing Overview
Product Version Purchase Instructions
Execute Resource Purchase Description
Billing Modes
Overdue Policy
Refund
Preparations
Overview of Account and Permission Management
Add allowlist /security groups (Optional)
Sign in to WeData with Microsoft Entra ID (Azure AD) Single Sign-On (SSO)
Operation Guide
Console Operation
Project Management
Data Integration
Studio
Data Development
Data Analysis
Data Science
Data Governance (with Unity Semantics)
API Documentation
History
Introduction
API Category
Making API Requests
Smart Ops Related Interfaces
Project Management APIs
Resource Group APIs
Data Development APIs
Data Asset - Data Dictionary APIs
Data Development APIs
Ops Center APIs
Data Operations Related Interfaces
Data Exploration APIs
Asset APIs
Metadata Related Interfaces
Task Operations APIs
Data Security APIs
Instance Operation and Maintenance Related Interfaces
Data Map and Data Dictionary APIs
Data Quality Related Interfaces
DataInLong APIs
Platform Management APIs
Data Source Management APIs
Data Quality APIs
Platform Management APIs
Asset Data APIs
Data Source Management APIs
Data Types
Error Codes
WeData API 2025-08-06
Service Level Agreements
Related Agreement
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary

Request Structure

PDF
Modo Foco
Tamanho da Fonte
Última atualização: 2026-03-13 12:14:11

1. Service Address

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

Ajuda e Suporte

Esta página foi útil?

comentários