Create an EDR configuration
POST/config/integrations/edr/configurations
Creates a configuration for one provider. The provider property selects the schema.
Send the body as JSON.
When config.integration.enabled is true the endpoint requires a valid base URL and credentials
for the provider, and returns 422 otherwise. When config.investigation.enabled is true a valid
config.investigation.base_url is required, and the 422 message names the "API Base URL". A request without a
recognized provider returns 422. When config.integration.use_proxy is true and enabled is true, a missing or invalid proxy configuration returns 409. name is required; a missing name, or a value that fails validation (for
example name or base_url over 255 characters, api_token over 1024 characters, a non-boolean enabled, an
unparsable Tanium tokenExpiresAt), returns 400. Names are not required to be unique: a second configuration with
the same name is created with 201. Release note: the product intends to reject duplicate active names with 409, but that check does not run for provider configurations, so duplicates are accepted.
Required role: superadmin or admin.
Request
Responses
- 201
- 400
- 401
- 403
- 409
- 422
Created. The body is a confirmation string, not the new object.
Validation failed (for example a value over its maximum length or of the wrong type).
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.