Job lifecycle
The HERE Batch API v7 handles requests asynchronously. When you submit a job, the response contains a jobId element. This indicates that the service has accepted the request and the value of the element is a unique identifier for a processing job that corresponds to the request. The service allocates addressable space to the job and uses it to store the request data as well as any output and status information. Use the jobId in building the path for your subsequent queries, for example, to retrieve job status and/or to trigger additional actions related to the job. The server stores jobs for 30 days after creation, which means you can re-retrieve previously completed jobs.
Possible job status is as follows:
- submitted
- queued
- pending
- inProgress
- completed
- failure
- stopped
- deleted
For more information on job statuses, see Job status.
To control jobs submitted to the HERE Batch API v7, use a combination of the jobId in the request and one of the supported action request parameter values (start, stop) or HTTP methods (GET, DELETE).
For more information, see API endpoints and Request parameters.
Possible state transitions are as shown in the diagram.
Updated 29 days ago