# Get anomaly detection jobs configuration info


**GET /_ml/anomaly_detectors/{job_id}**

**All methods and paths for this operation:**

<div>
                      <span class="operation-verb get">GET</span>
                      <span class="operation-path">/_ml/anomaly_detectors</span>
                      </div>
                    <div>
                      <span class="operation-verb get">GET</span>
                      <span class="operation-path">/_ml/anomaly_detectors/{job_id}</span>
                      </div>
                    

You can get information for multiple anomaly detection jobs in a single API
request by using a group name, a comma-separated list of jobs, or a wildcard
expression. You can get information for all anomaly detection jobs by using
`_all`, by specifying `*` as the `<job_id>`, or by omitting the `<job_id>`.

## Required authorization

* Cluster privileges: `monitor_ml`



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


## Authentication methods
- Api key auth
- Basic auth
- Bearer auth


## Parameters

### Path parameters
- **job_id** (string | array[string])
  Identifier for the anomaly detection job. It can be a job identifier, a
  group name, or a wildcard expression. If you do not specify one of these
  options, the API returns information for all anomaly detection jobs.

### Query parameters
- **allow_no_match** (boolean)
  Specifies what to do when the request:

  1. Contains wildcard expressions and there are no jobs that match.
  2. Contains the _all string or no identifiers and there are no matches.
  3. Contains wildcard expressions and there are only partial matches.

  The default value is `true`, which returns an empty `jobs` array when
  there are no matches and the subset of results when there are partial
  matches. If this parameter is `false`, the request returns a `404` status
  code when there are no matches or only partial matches.
- **exclude_generated** (boolean)
  Indicates if certain fields should be removed from the configuration on
  retrieval. This allows the configuration to be in an acceptable format to
  be retrieved and then added to another cluster.


## Responses
### 200


#### Body: application/json (object)
- **count** (number)

- **jobs** (array[object])



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