Test an EDR connection
POST/config/integrations/edr/configurations/validate
Tests the integration settings against the provider ("Test Connection").
The body has the same shape as create, and provider is always required (a missing or unknown provider returns 422, even with _id). Include _id of an existing configuration, together with its provider, to reuse its stored secrets for values the body omits; omit _id to test an unsaved configuration. A malformed _id returns 422. Only config.integration is tested. If the body has no config.integration, the response is 200 with an empty body. The body is not schema-validated (no 400 for wrong types).
The HTTP status is 200 whether or not the connection works; read success (or the per-API flags
for Carbon Black Cloud) and messages in the body. Invalid input returns 422, an unusable proxy returns 409.
Required role: superadmin or admin.
Request
Responses
- 200
- 401
- 403
- 409
- 422
Test outcome.
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).
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.