How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Yunqi (ClickZetta / Singdata Lakehouse) Data Source API

数据源连接管理

Yunqi (ClickZetta / Singdata Lakehouse) Data Source API is one of 9 APIs that Yunqi (ClickZetta / Singdata Lakehouse) publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include DataSource. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 7 operations across 7 paths, and defines 30 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://api.clickzetta.com, https://api.singdata.com.

7 operations 7 paths 30 schemas 7 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.clickzetta.com
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Yunqi (ClickZetta / Singdata Lakehouse) Data Source API declares 2 security schemes for authenticating requests. An API key is passed in the header as accessKey (AccessKeyID). An API key is passed in the header as sign (RequestSignature). By default, every request must be authenticated.

  • AccessKeyID — Access Key ID。与 RequestSignature 同时使用;不要填写 Access Key Secret。
  • RequestSignature — 使用 AK/SK 自定义请求签名认证。accessKey 是 Access Key ID,sign 是每次请求动态生成的签名;Access Key Secret 只在客户端参与签名,不随请求发送。请求头与查询参数由官方 SDK 生成。SDK 使用 HMAC-SHA1 计算签名,查询参数 SignatureMethod…

Paths & Operations 7

Across 7 paths, the API surfaces 7 operations — 7 POST. Each is listed below with its method, path, parameters, and response codes.

DataSource 7

数据源连接管理

POST
/openapi/v2/datasource/get
查询数据源详情
getDataSource 11 params body → 200
POST
/openapi/v2/datasource/update
更新数据源
updateDataSource 11 params body → 200
POST
/openapi/v2/datasource/test
测试数据源连通性
testDataSource 11 params body → 200
POST
/openapi/v2/datasource/list
查询数据源列表
listDataSource 11 params body → 200
POST
/openapi/v2/datasource/getPublicKey
获取公钥
getPublicKey 11 params → 200
POST
/openapi/v2/datasource/create
创建数据源
createDataSource 11 params body → 200
POST
/openapi/v2/datasource/delete
删除数据源
deleteDataSource 11 params body → 200

Schemas 30

The contract defines 30 schemas that model the data the API accepts and returns. The most detailed are HiveConnectionParams (19 properties), DataSourceMeta (17 properties), DorisConnectionParams (15 properties), JdbcConnectionParams (10 properties). Each schema is shown below with its type and property counts.

AmqpConnectionParams
object
8 properties 8 required
DsType
object
1 property
KafkaConnectionParams
object
8 properties 8 required
CosConnectionParams
object
4 properties 4 required
DataSourceUpdateResponse
object
5 properties 4 required
UpdateMark
object
1 property 1 required
HiveConnectionParams
object
19 properties 19 required
DataSourceListResponse
object
5 properties 4 required
ObservedAuthenticationError
object
三个只读接口已观测到的未认证响应:HTTP 200,code 为 401,可能没有 success 字段。此模型只描述该已观测情形。
4 properties 4 required
DataSourceDeleteRequest
object
3 properties 1 required
DataSourceTestRequest
object
5 properties 3 required
DataSourceMeta
object
17 properties 1 required
StringDataResponse
object
5 properties 5 required
DataSourceGetRequest
object
3 properties 1 required
OdpsConnectionParams
object
5 properties 5 required
DataSourceUpdateRequest
object
8 properties 4 required
DataSourceCreateRequest
object
6 properties 4 required
OssConnectionParams
object
4 properties 4 required
BooleanDataResponse
object
5 properties 4 required
HbaseConnectionParams
object
8 properties 7 required
MongodbConnectionParams
object
9 properties 9 required
DataSourceGetResponse
object
5 properties 4 required
JdbcConnectionParams
object
10 properties 3 required
DataSourceListRequest
object
8 properties 4 required
LoghubConnectionParams
object
4 properties 4 required
ElasticSearchConnectionParams
object
9 properties 9 required
TestMark
object
1 property 1 required
DataSourceCreateResponse
object
5 properties 4 required
CreateMark
object
1 property 1 required
DorisConnectionParams
object
15 properties 15 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

yunqi-datasource-api-openapi.yml Raw ↑

Other APIs Yunqi (ClickZetta / Singdata Lakehouse) publishes across the network.

Yunqi (ClickZetta / Singdata Lakehouse) Dqc API
Yunqi (ClickZetta / Singdata Lakehouse) Instance API
Yunqi (ClickZetta / Singdata Lakehouse) Multi Realtime Di Task API
Yunqi (ClickZetta / Singdata Lakehouse) Realtime Task API
Yunqi (ClickZetta / Singdata Lakehouse) Schedule Task API
Yunqi (ClickZetta / Singdata Lakehouse) User Management API
Yunqi (ClickZetta / Singdata Lakehouse) Virtual Cluster API
Yunqi (ClickZetta / Singdata Lakehouse) Workspace API
Where this information came from

This is an independent, third-party profile of Yunqi (ClickZetta / Singdata Lakehouse) Data Source API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.