Delete an EDR configuration
DELETE/config/integrations/edr/configurations/:id
Soft-deletes the configuration: active becomes false and the name is renamed to <name>_deleted_<unix-ms> so the name can be reused.
Deleting an already deleted configuration succeeds with no further change. Returns 409 when a domain (LDAP or Microsoft Entra ID) or a system still uses the configuration. Required role: superadmin or admin.
Request
Responses
- 200
- 401
- 403
- 404
- 409
- 422
Outcome of the soft delete.
No token, or the token is invalid or expired. The body is {message}: No auth token provided when no token is sent, otherwise the token check's message (jwt expired, jwt malformed, invalid signature, invalid token, jwt signature is required). Send Authorization: Bearer <token> exactly: the server drops the first seven characters of the header and reads the rest as the token, so a different scheme or an extra space fails. If Authorization is absent, the server reads a token field in the body, then a token query parameter, then x-access-token. Routes that validate query fields reject ?token= with 400 InvalidQuery.
The token's role is not allowed for this operation, or the token's scopes exclude the route
(Scope not allowed by token).
No configuration with this id.
The request conflicts with the current state of the resource.
The request could not be processed, for example an id that is not a valid object id.