You need to enable JavaScript to run this app.
Database Workshop

Database Workshop

Copy page
Download PDF
Call method
Request structure
Copy page
Download PDF
Request structure
This topic introduces the API request structure information of Database Workshop (DBW).​
Endpoints​
The regions currently opened are shown in the table below.​
​
Region​
​
RegionId​
Endpoints​
China​
China (Shanghai)​
cn-shanghai​
dbw.cn-shanghai.volcengineapi.com​
​
China (Beijing)​
cn-beijing​
dbw.cn-beijing.volcengineapi.com​
​
China (Guangzhou)​
cn-guangzhou​
dbw.cn-guangzhou.volcengineapi.com​
​
China (Hong Kong)​
cn-hongkong​
dbw.cn-hongkong.volcengineapi.com​
Overseas​
Asia Pacific (Johor)​
ap-southeast-1​
dbw.ap-southeast-1.volcengineapi.com​
​
Asia Pacific (Jakarta)​
ap-southeast-3​
dbw.ap-southeast-3.volcengineapi.com​
​
tip​
  • For latency-sensitive services, it is suggested to specify the Region in the request Header. For details, refer to Common parameters.​
  • The domain name is the access point of the API and does not represent the region where the product or service is actually provided.​
Communication protocol​
Both HTTP and HTTPS request communication methods are supported. It is recommended that you use the more secure HTTPS method to send requests.​
Request method​
The HTTP POST request method is supported. Specifically, the supported Content-Type of POST requests is application/JSON (recommended).​
tip​
All requests must adopt the Volcano Engine Signature mechanism.​
Request parameters​
Each API request contains the following two types of parameters:​
  • Common request parameters: A parameter that is used by every API is a common request parameter. For more details about common request parameters, refer to Common parameters.​
  • API-specific request parameters: Parameters specific to each API. For more information on the request parameters of each API, refer to the API descriptions in API overview.​
Character encoding​
UTF-8 encoding is used for all requests.​
​
Last updated: 2026.09.01 16:57:38