tencent cloud

Data Lake Compute

Release Notes
Product Introduction
Overview
Strengths
Use Cases
Purchase Guide
Billing Overview
Refund
Payment Overdue
Configuration Adjustment Fees
Getting Started
Complete Process for New User Activation
DLC Data Import Guide
Quick Start with Data Analytics in Data Lake Compute
Quick Start with Permission Management in Data Lake Compute
Quick Start with Partition Table
Enabling Data Optimization
Cross-Source Analysis of EMR Hive Data
Standard Engine Configuration Guide
Configuring Data Access Policy
Operation Guide
Console Operation Introduction
Development Guide
Runtime Environment
SparkJar Job Development Guide
PySpark Job Development Guide
Query Performance Optimization Guide
UDF Function Development Guide
System Restraints
Client Access
JDBC Access
TDLC Command Line Interface Tool Access
Third-party Software Linkage
Python Access
Practical Tutorial
Accessing DLC Data with Power BI
Table Creation Practice
Using Apache Airflow to Schedule DLC Engine to Submit Tasks
Direct Query of DLC Internal Storage with StarRocks
Spark cost optimization practice
DATA + AI
Using DLC to Analyze CLS Logs
Using Role SSO to Access DLC
Resource-Level Authentication Guide
Implementing Tencent Cloud TCHouse-D Read and Write Operations in DLC
DLC Native Table
SQL Statement
SuperSQL Statement
Overview of Standard Spark Statement
Overview of Standard Presto Statement
Reserved Words
API Documentation
History
Introduction
API Category
Making API Requests
Data Table APIs
Task APIs
Metadata APIs
Service Configuration APIs
Permission Management APIs
Database APIs
Data Source Connection APIs
Data Optimization APIs
Data Engine APIs
Resource Group for the Standard Engine APIs
Data Types
Error Codes
General Reference
Error Codes
Quotas and limits
Operation Guide on Connecting Third-Party Software to DLC
FAQs
FAQs on Permissions
FAQs on Engines
FAQs on Features
FAQs on Spark Jobs
DLC Policy
Privacy Policy
Data Privacy And Security Agreement
Service Level Agreement
Contact Us
DocumentationData Lake ComputeAPI DocumentationMaking API RequestsRequest Structure

Request Structure

PDF
Focus Mode
Font Size
Last updated: 2025-11-13 20:53:13

1. Service Address

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

Previous Topic: API CategoryNext Topic: Common Params

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback