---
title: "Get a job's constraints"
method: GET
path: "/v1/jobs/{jobId}/constraints"
tags: ["Jobs"]
---

# Get a job's constraints

`GET /v1/jobs/{jobId}/constraints`

Retrieve a paged collection of a job's constraints (required scope jobs:read)

## Path parameters

- `jobId` integer, required

## Query parameters

- `sortBy` 'createdAt' — Represents the fields that can be used to sort job constraint<p>Possible values:</p><ul><li><b>createdAt</b>: The date and time when the job constraint was created</li></ul>
- `direction` 'ascending' | 'descending' — Represents the direction in which sorting should be applied<p>Possible values:</p><ul><li><b>ascending</b>: Indicates ascending sorting order</li><li><b>descending</b>: Indicates descending sorting order</li></ul>
- `pageNumber` integer
- `pageSize` integer

## Headers

- `Customer-Id` integer, required

## Response `200`

OK

- PagedResponseReadJobStatusModel — A paged collection of items
  - `items` ReadJobStatusModel[] — The items returned for the requested page
    - `id` integer — The unique identifier of the job status change
    - `status` 'new' | 'scheduled' | 'unscheduled' | 'sent' | 'read' | 'accepted' | 'refused' | 'onTheWay' | 'started' | 'suspended' | 'completedOk' | 'completedWithIssues' | 'cancelled' | 'lateStart' | 'lateFinish' | 'rescheduled' — Describes each possible status of a Job<p>Possible values:</p><ul><li><b>new</b>: A job that is newly created in BigChange All Jobs start with a New status, regardless of schedule detail</li><li><b>scheduled</b>: Job has been scheduled. Scheduled status is when the Vehicle, Driver, and Planned Date Time are all allocated</li><li><b>unscheduled</b>: Job has been unscheduled. Unscheduled status happens when any combination of the Vehicle, Driver, and Planned Date Time are all removed from a Scheduled job</li><li><b>sent</b>: The scheduled job has been delivered to the driver's mobile device (tablet/phone). The driver must be logged into BigChange for jobs to be sent</li><li><b>read</b>: Job Detail has been read by the Driver on their mobile terminal</li><li><b>accepted</b>: Driver accepted the job</li><li><b>refused</b>: Driver refused the job</li><li><b>onTheWay</b>: Driver indicated they are on route to the Job Address</li><li><b>started</b>: Driver has indicated they have started the work detailed in the Job</li><li><b>suspended</b>: Driver paused work – ie taking a break</li><li><b>completedOk</b>: Job Completed with no issues</li><li><b>completedWithIssues</b>: Job Completed with issues</li><li><b>cancelled</b>: Job was Cancelled</li><li><b>lateStart</b>: Internal Status used by BigChange Alert Management - should not be visible from the the API</li><li><b>lateFinish</b>: Internal Status used by BigChange Alert Management - should not be visible from the the API</li><li><b>rescheduled</b>: Internal Status used by BigChange Alert Management - should not be visible from the the API</li></ul>
    - `createdAt` string, date-time — The UTC timestamp of when this job status history entry was created (when the job status changed)
    - `actionedBy` string — The name of the user who triggered the change in status
    - `comment` string — Textual context about the status change that was made
  - `pageNumber` integer — The page number of the response where 1 is the first page
  - `pageSize` integer — The number of items requested for the current page
  - `pageItemCount` integer — The number of items returned in the current page

## Other responses

- `400` — Bad Request
- `403` — Forbidden
- `404` — Not Found
- `500` — Internal Server Error

---

[API](https://skmtc.net/bigchange/apis/bigchange-dx.md) · [All operations](https://skmtc.net/bigchange/apis/bigchange-dx/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/bigchange/bigchange-dx/revisions/916e669fc527/schema)