---
title: "This V2 version checks status of requested job of bulk geocode/verify"
method: GET
path: "/v2/bulk/jobs/{jobId}"
tags: ["Bulk Geo Addressing"]
---

# This V2 version checks status of requested job of bulk geocode/verify

`GET /v2/bulk/jobs/{jobId}`

## Request

- Base URL: `https://api.cloud.precisely.com`
- URL: `https://api.cloud.precisely.com/v2/bulk/jobs/{jobId}`
- Auth: one of:
  - HTTP bearer
  - API key in header `Authorization`

This V2 version API checks status of requested job of bulk geocode/verify. It takes the job id provided when we submit bulk geocode/verify job and returns the status of the job. Once the job is completed it returns download url of output file along with status.

## Path parameters

- `jobId` string, required

## Headers

- `X-Request-Id` string

## Response `200`

Status got successfully

- JobStatusResponse: Job status response
  - `status` 'SCHEDULED' | 'RUNNING' | 'COMPLETED' | 'FAILED' | 'CANCELED' | 'REJECTED', required: status of the job
  - `downloadUrl` string, url: url for downloading the output file of the Bulk Geocode/Verify
  - `reportUrl` string, url: url for downloading the report file of the Bulk Geocode/Verify
  - `message` string: message for the response
  - `error` string: Error message of the Job

## Other responses

- `400`: Invalid request for Bulk Job Status API
- `401`: Unauthorized: Invalid token for Bulk Job Status API
- `403`: Forbidden for Bulk Job Status API
- `429`: Too many requests for Bulk Job Status API
- `500`: Internal Server Error for Bulk Job Status API

---

[API](https://skmtc.dev/precisely/apis/bulk-geo-addressing-api.md) · [All operations](https://skmtc.dev/precisely/apis/bulk-geo-addressing-api/llms.txt) · [OpenAPI document](https://skmtc.dev/precisely/apis/bulk-geo-addressing-api/revisions/aad307eeb518?raw)
