# Delete an anomaly detection job

**DELETE /_ml/anomaly_detectors/{job_id}**

All job configuration, model state and results are deleted.
It is not currently possible to delete multiple jobs using wildcards or a
comma separated list. If you delete a job that has a datafeed, the request
first tries to delete the datafeed. This behavior is equivalent to calling
the delete datafeed API with the same timeout and force parameters as the
delete job request.

## Required authorization

* Cluster privileges: `manage_ml`



## Servers
- http://api.example.com: http://api.example.com ()


## Authentication methods
- Api key auth


## Parameters

### Path parameters
- **job_id** (string)
  Identifier for the anomaly detection job.

### Query parameters
- **force** (boolean)
  Use to forcefully delete an opened job; this method is quicker than
  closing and deleting the job.
- **delete_user_annotations** (boolean)
  Specifies whether annotations that have been added by the
  user should be deleted along with any auto-generated annotations when the job is
  reset.
- **wait_for_completion** (boolean)
  Specifies whether the request should return immediately or wait until the
  job deletion completes.


## Responses
### 200


#### Body: application/json (object)
- **acknowledged** (boolean)
  For a successful response, this value is always true. On failure, an exception is returned instead.


[Powered by Bump.sh](https://bump.sh)