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) Schedule Task API

调度任务与组合任务管理

Yunqi (ClickZetta / Singdata Lakehouse) Schedule Task 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 ScheduleTask. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 30 operations across 30 paths, and defines 75 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.

30 operations 30 paths 75 schemas 30 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) Schedule Task 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 30

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

ScheduleTask 30

调度任务与组合任务管理

POST
/openapi/v2/scheduler/task/add
创建任务
createTask 11 params body → 200
POST
/openapi/v2/scheduler/task/saveContent
保存任务脚本
saveTaskContent 11 params body → 200
POST
/openapi/v2/scheduler/task/saveConfig
保存调度配置
saveTaskConfig 11 params body → 200
POST
/openapi/v2/scheduler/task/lastRecord
查询最近实例记录
fetchTaskLastInstanceRecord 11 params body → 200
POST
/openapi/v2/scheduler/task/lastLog
查询实例最近日志
fetchTaskInstanceLastLog 11 params body → 200
POST
/openapi/v2/scheduler/task/delete
删除任务
deleteTask 11 params body → 200
POST
/openapi/v2/scheduler/task/adhoc/execute
即席执行任务
taskAdhocExecute 11 params body → 200
POST
/openapi/v2/scheduler/task/kill
终止即席实例
killAdhocTaskInstance 11 params body → 200
POST
/openapi/v2/scheduler/task/adhocLastRecord
查询即席实例记录
fetchAdhocTaskInstanceLastRecord 11 params body → 200
POST
/openapi/v2/scheduler/task/adhocResult
查询即席实例结果
fetchAdhocTaskInstanceResult 11 params body → 200
POST
/openapi/v2/scheduler/task/submit
提交任务
submitTask 11 params body → 200
POST
/openapi/v2/scheduler/task/offline
下线任务
offlineTask 11 params body → 200
POST
/openapi/v2/scheduler/task/rerun
重跑实例
rerunTaskInstance 11 params body → 200
POST
/openapi/v2/scheduler/task/getDetail
查询任务详情
getTaskDetail 11 params body → 200
POST
/openapi/v2/scheduler/task/list
查询任务列表
listTasks 11 params body → 200
POST
/openapi/v2/scheduler/task/instance/list
查询实例列表
listTaskInstances 11 params body → 200
POST
/openapi/v2/scheduler/task/execute
执行任务
executeTask 11 params body → 200
POST
/openapi/v2/scheduler/task/suspend
暂停任务
suspendTask 11 params body → 200
POST
/openapi/v2/scheduler/task/resume
恢复任务
resumeTask 11 params body → 200
POST
/openapi/v2/scheduler/folder/add
创建文件夹
createFolder 11 params body → 200201401403404
POST
/openapi/v2/scheduler/folder/list
查询文件夹列表
listFolder 11 params body → 200201401403404
POST
/openapi/v2/scheduler/flow/node/add
创建 Flow 节点
flowNodeCreate 11 params body → 200
POST
/openapi/v2/scheduler/flow/node/remove
移除 Flow 节点
flowNodeRemove 11 params body → 200
POST
/openapi/v2/scheduler/flow/node/bind
绑定节点依赖
flowNodeBind 11 params body → 200
POST
/openapi/v2/scheduler/flow/node/unbind
解绑节点依赖
flowNodeUnbind 11 params body → 200
POST
/openapi/v2/scheduler/flow/submit
提交 Flow
flowSubmit 11 params body → 200
POST
/openapi/v2/scheduler/flow/checkSubmitStatus
查询 Flow 提交状态
flowSubmitStatusCheck 11 params body → 200
POST
/openapi/v2/scheduler/flow/getDag
获取 Flow DAG
flowDagGet 11 params body → 200
POST
/openapi/v2/scheduler/flow/adhoc/execute
即席执行 Flow
flowAdhocExecute 11 params body → 200
POST
/openapi/v2/scheduler/flow/node/queryAdhocInstance
查询 Flow 节点实例
flowNodeInstanceQuery 11 params body → 200

Schemas 75

The contract defines 75 schemas that model the data the API accepts and returns. The most detailed are TaskInstanceListResult (63 properties), TaskDataFileDetailResult (41 properties), FlowNodeInstanceResult (38 properties), TaskAdhocExecuteRequest (36 properties). Each schema is shown below with its type and property counts.

TaskDataFileDetailResponse
object
5 properties 5 required
TaskInstanceRerunRequest
object
7 properties 3 required
TaskDataFileInfoListRequest
object
18 properties 4 required
TaskConfigSaveRequest
object
25 properties 11 required
FolderQueryRequest
object
10 properties
TaskDataFileDetailResult
object
41 properties
FolderQueryResponse
object
5 properties 4 required
TaskLastLogFetchRequest
object
7 properties 4 required
TaskRerunExecuteResponse
object
5 properties 4 required
TaskAdhocRecordRequest
object
7 properties 4 required
FlowNodeBindRequest
object
绑定流程节点的请求参数
9 properties 1 required
TaskAdhocRecordResponse
object
5 properties 4 required
TaskCreateRequest
object
10 properties 3 required
FlowSubmitRequest
object
提交流程请求的参数
6 properties 2 required
FlowSubmitResponse
object
5 properties 4 required
TaskParamValue
object
5 properties
TaskAdhocExecuteResult
object
9 properties
FlowNodeCreateRequest
object
12 properties 4 required
FlowNodeRemoveRequest
object
删除流程节点的请求参数
4 properties
TaskAdhocExecuteRequest
object
临时查询执行请求
36 properties 2 required
TaskAdhocDataResponse
object
5 properties 4 required
TaskAdhocRecordResult
object
6 properties 2 required
FlowNodeUnbindRequest
object
解绑流程节点的请求参数
4 properties
DataFileDagResult
object
数据文件 DAG 视图对象
34 properties
TaskAdhocDataResult
object
3 properties 3 required
TaskDataFileListResponse
object
5 properties 4 required
FlowSubmitStatusResponse
object
5 properties 5 required
TaskCreateResponse
object
5 properties 4 required
FlowNodeBindResponse
object
5 properties 4 required
FlowSubmitStatusRequest
object
1 property 1 required
FolderCreateResponse
object
5 properties 4 required
DataFileDependencyResult
object
数据文件依赖项 DTO
19 properties
TaskSuspendRequest
object
6 properties 3 required
FlowNodeInstanceQueryResponse
object
5 properties 4 required
TaskDeleteRequest
object
6 properties 3 required
TaskLastLogFetchResponse
object
5 properties 5 required
TaskInstanceListRequest
object
24 properties 5 required
TaskLastRecordFetchRequest
object
7 properties 3 required
TaskInstanceListResult
object
63 properties
TaskCreateResult
object
1 property 1 required
TaskLastLogFetchResult
object
1 property 1 required
DataFileCoordResult
object
数据文件坐标 DTO
2 properties
TaskLastResultFetchResult
object
14 properties 2 required
TaskOfflineRequest
object
6 properties 3 required
FlowParamValues
object
流程参数值 DTO
4 properties
TaskLastResultFetchResponse
object
5 properties 4 required
TaskExecuteResponse
object
5 properties 4 required
TaskRerunExecuteResult
object
1 property 1 required
TaskContentSaveRequest
object
10 properties 4 required
BooleanDataResponse
object
5 properties 4 required
TaskInstanceListResponse
object
5 properties 4 required
TaskAdhocResultRequest
object
3 properties 1 required
FlowNodeInstanceResult
object
流程节点实例 DTO
38 properties
FolderCreateRequest
object
7 properties 3 required
TaskExecuteResult
object
1 property
FlowNodeRemoveResponse
object
5 properties 4 required
DataTaskInput
object
1 property
TaskIdRequest
object
1 property 1 required
FlowDagResponse
object
5 properties 4 required
ParamValue
object
参数值 DTO
10 properties
TaskDataFileInfoResult
object
18 properties 12 required
FlowSubmitStatus
object
1 property 1 required
ObservedAuthenticationError
object
三个只读接口已观测到的未认证响应:HTTP 200,code 为 401,可能没有 success 字段。此模型只描述该已观测情形。
4 properties 4 required
FlowNodeUnbindResponse
object
5 properties 4 required
CommonDs
object
通用数据源 DTO
5 properties
FlowBaseRequest
object
5 properties 2 required
TaskAdhocExecuteResponse
object
5 properties 4 required
FolderQueryResult
object
14 properties 12 required
TaskExecuteRequest
object
6 properties 4 required
TaskResumeRequest
object
6 properties 3 required
FlowNodeCreateResponse
object
5 properties 4 required
TaskDataFileDetailRequest
object
8 properties 3 required
TaskSubmitRequest
object
6 properties 3 required
TaskAdhocKillRequest
object
6 properties 3 required
FolderCreateResult
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

yunqi-scheduletask-api-openapi.yml Raw ↑

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

Yunqi (ClickZetta / Singdata Lakehouse) Data Source API
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) 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) Schedule Task 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.