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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Chaitin Tech

Chaitin Tech 任务/任务实例v2 API

The 任务/任务实例v2 API from Chaitin Tech — 14 operation(s) for 任务/任务实例v2.

Documentation Provider Profile APIs.io OpenAPI GitHub

Chaitin Tech 任务/任务实例v2 API is one of 556 APIs that Chaitin Tech publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include v2. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

This API exposes 17 operations across 14 paths. It is described by OpenAPI 3.2.0, at version 26.05.

Requests are made against a single base URL, https://docs.waf.chaitin.com.

17 operations 14 paths 0 schemas 2 DELETE9 GET1 PATCH5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
26.05
Base URL
https://docs.waf.chaitin.com
Resource Areas
1

Paths & Operations 17

Across 14 paths, the API surfaces 17 operations — 2 DELETE, 9 GET, 1 PATCH, 5 POST. Each is listed below with its method, path, parameters, and response codes.

任务/任务实例v2 17
GET
/v1/task/{task_type}/instance
任务实例列表
6 params → 200
POST
/v1/task/{task_type}/instance
任务实例创建（立即运行）
2 params body → 200
DELETE
/v1/task/{task_type}/instance/batch-delete
任务实例批量删除
2 params body → 200
POST
/v1/task/{task_type}/instance/status
任务实例批量重跑、暂停
2 params body → 200
GET
/v1/task/{task_type}/instance/status/count
任务实例状态数量
2 params → 200
GET
/v1/task/{task_type}/instance/{id}
任务实例查看
3 params → 200
GET
/v1/task/attack/schedule/xapp/options
指纹分组选项
1 param → 200
GET
/v1/task/risk/schedule/xpoc/options
漏洞分组选项
1 param → 200
GET
/v1/task/{task_type}/schedule
周期任务列表
6 params → 200
POST
/v1/task/{task_type}/schedule
周期任务创建
2 params body → 200
DELETE
/v1/task/{task_type}/schedule/batch-delete
周期任务批量删除
2 params body → 200
POST
/v1/task/{task_type}/schedule/status
周期任务批量切换状态
2 params body → 200
GET
/v1/task/{task_type}/schedule/{id}
周期任务查看
3 params → 200
PATCH
/v1/task/{task_type}/schedule/{id}
周期任务编辑
3 params body → 200
GET
/v1/task/{task_type}/flow
编排实例列表
4 params → 200
POST
/v1/task/{task_type}/flow/reboot
编排实例批量重跑
2 params body → 200
GET
/v1/task/{task_type}/flow/status/count
编排实例状态数量
3 params → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

chaitin-v2-api-openapi.yml Raw ↑

Other APIs Chaitin Tech publishes across the network.

Chaitin Tech account API
AE Profile APIs.io
Chaitin Tech account/staff_devices/{staff_id}/add API
AE Profile APIs.io
Chaitin Tech account/staff_devices/{staff_id}/remove API
AE Profile APIs.io
Chaitin Tech account/staff/list API
AE Profile APIs.io
Chaitin Tech account/staff/{staff_id}/fav API
AE Profile APIs.io
Chaitin Tech account/staff_tag API
AE Profile APIs.io
Chaitin Tech account/staff_tag/list API
AE Profile APIs.io
Chaitin Tech account/staff_tags/{staff_id}/bind API
AE Profile APIs.io
Chaitin Tech account/tag/modify API
AE Profile APIs.io
Chaitin Tech analyse/expression/classification API
AE Profile APIs.io
Chaitin Tech analyse/expression/classification/batch API
AE Profile APIs.io
Chaitin Tech analyse/filecut API
AE Profile APIs.io
#v2
← Back to C APIs
API Details
ID
chaitin:chaitin-v2-api
Base URL
https://docs.waf.chaitin.com
Docs
https://docs.waf.chaitin.com/en/tech_docs/OPENAPI
Provider
Chaitin Tech
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=chaitin-v2-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/chaitin-v2-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Chaitin Tech 任务/任务实例v2 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.