# Get Job Status

This page describes the `jobs` endpoint.

{% hint style="info" %}
Additional fields may be included in some responses you receive; however, these attributes are for internal purposes and are therefore undocumented.
{% endhint %}

## Get job status and output

<mark style="color:green;">`POST`</mark> `/jobs/statuses`

Get the status and output of the provided jobs.

#### Payload parameters

| Attribute    | Description                                                                                                                                     | Required |
| ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------- | -------- |
| jobIds       | `string` List of job IDs.                                                                                                                       | **Yes**  |
| wait         | `integer` Number of seconds to wait before returning if all jobs have not yet completed. Use `-1` to wait indefinitely. **The default is `0`.** | No       |
| pollInterval | `integer` Number of seconds to wait between subsequent polls. Ignored if not using `wait`. **The default is `1`. The minimum is `1`.**          | No       |

#### Response parameters

| Attribute | Description                                                                                                    |
| --------- | -------------------------------------------------------------------------------------------------------------- |
| id        | `string` The job's globally unique identifier.                                                                 |
| state     | `array[string]` The job state: `active`, `cancelled`, `completed`, `created`, `expired`, `failed`, or `retry`. |
| output    | `string` The output of the job, if it exists.                                                                  |

### Request example

The following request checks the status of the job specified in the payload.

```shell
curl \
    --request POST \
    --header "Content-Type: application/json" \
    --header "Authorization: Bearer dea464c07bd07300095caa8" \
    --data @example_payload.json
    https://your-immuta-url.com/jobs/statuses
```

#### Payload example

```json
{
  "jobIds": [
    "cefb58a0-cd71-11ec-8e29-81c20d280994"
  ],
  "wait": 0,
  "pollInterval": 1
}
```

### Response example

```json
{
  "cefb58a0-cd71-11ec-8e29-81c20d280994": {
    "id": "cefb58a0-cd71-11ec-8e29-81c20d280994",
    "state": "completed",
    "output": null
  }
}
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://documentation.immuta.com/2024.3/developer-guides/api-intro/immuta-v1-api/configure-your-instance-of-immuta/jobs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.