---
title: "Start processing a batch job"
method: POST
path: "/jobs/{job_id}/results"
tags: ["Data Processing", "Batch Jobs"]
---

# Start processing a batch job

`POST /jobs/{job_id}/results`

Adds a batch job to the processing queue to compute the results.

The result will be stored in the format specified in the process.
To specify the format use a process such as `save_result`.

The job status is set to `queued`, if processing does not start
instantly. The same applies if the job status is `canceled`, `finished`,
or `error`, which restarts the job and discards previous results if the
back-end does not reject the request with an error.
Clients SHOULD warn users and ask for confirmation if results may get
discarded.

* Once the processing starts the status is set to `running`.
* Once the data is available to download the status is set to
`finished`.
* Whenever an error occurs during processing, the status MUST be set to
`error`.

This endpoint has no effect if the job status is already `queued` or
`running`. In particular, it does not restart a running job. To restart
a queued or running job, processing MUST have been canceled.

Back-ends SHOULD reject queueing jobs with openEO error `PaymentRequired`,
if the back-end is able to detect that the budget is too low to fully
process the request. Alternatively, back-ends MAY provide partial results
once reaching the budget. If none of the alternatives is feasible, the
results are discarded. Thus, client SHOULD warn users that reaching the
budget may lead to partial or no results at all.

## Response `202`

The creation of the resource has been queued successfully.

## Other responses

- `4XX` — The request can not be fulfilled due to an error on client-side, i.e. the request is invalid. The client SHOULD NOT repeat the request without modifications. The response body SHOULD contain a JSON error object. MUST be any HTTP status code specified in [RFC 7231](https://www.rfc-editor.org/rfc/rfc7231.html#section-6.6). This request MUST respond with HTTP status codes 401 if authorization is required or 403 if the authorization failed or access is forbidden in general to the authenticated user. HTTP status code 404 SHOULD be used if the value of a path parameter is invalid. See also: * [Error Handling](#section/API-Principles/Error-Handling) in the API in general. * [Common Error Codes](errors.json)
- `5XX` — The request can not be fulfilled due to an error at the back-end. The error is never the client’s fault and therefore it is reasonable for the client to retry the exact same request that triggered this response. The response body SHOULD contain a JSON error object. MUST be any HTTP status code specified in [RFC 7231](https://www.rfc-editor.org/rfc/rfc7231.html#section-6.6). See also: * [Error Handling](#section/API-Principles/Error-Handling) in the API in general. * [Common Error Codes](errors.json)

---

[API](https://skmtc.net/open-eo/apis/openeo-api.md) · [All operations](https://skmtc.net/open-eo/apis/openeo-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/open-eo/openeo-api/versions/0c5e31955a19/schema)