Interface DetectAnomaliesRequest

The input is either:

• JSON object in the request. This object is defined and SDK will generate the object for it
• Data embedded as Base64 string in format of either
  • CSV
  • JSON If this option is chosen then customer has to provide the content of specified CSV or JSON in Base64 encoded string. The Embedded JSON will still has to be in same format as inline request JSON

For optimistic concurrency control. In the PUT or DELETE call for a resource, set the {@code if-match} parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource's current etag value.

The client request ID for tracing.

A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.