Delete Detection Config
Delete one detection config so it stops scanning. Other configs sharing the same source keep running. Deleting the last config for a source that is enabled by default is not permanent, since automation re-creates it; disable it through /detection/configs/update instead.
Overview
Soft-delete one org-scoped threat detection config byconfigId so it stops
scanning. Other configs sharing the same source keep running.
Only configs owned by your organization can be deleted through this endpoint;
global configs stay staff-only.
When to use
- Remove a config you no longer need.
- Retire one variant of a multi-config source without touching the others.
status set to DISABLED instead — automation will not override that.
How it works
- Look up the
configIdwith List Detection Configs. - The config’s
deletedAtandupdatedAtare set, and a history row is written with unchanged status so default-sync jobs don’t treat the deletion as a status change.
Authorizations
Your API key. This is required by most endpoints to access our API programatically. Reach out to us at support@chainpatrol.io to get an API key for your use.
Body
Delete a threat detection config
Deletes one detection config so it stops scanning. Deleting a config that shares a source with others leaves the others running.
Deleting the last config for a source that is enabled by default for your organization is not permanent: automation re-creates a default config for that source on its next run. To stop such a source durably, set status to DISABLED through /detection/configs/update instead, which automation will not override.