---
title: "Get Job Change History"
method: GET
path: "/jobs/{jobId}/history"
tags: ["jobs"]
---

# Get Job Change History

`GET /jobs/{jobId}/history`

Use this endpoint to get a history of actions performed for a job. **Supported includes:** `createdBy`. When startDate and endDate are specified, actions returned will be filtered to those created between those dates (inclusive). This endpoint will return a paginated response starting from the given record index.

## Path parameters

- `jobId` string, uuid, required

## Query parameters

- `pageSize` integer
- `recordStartIndex` integer
- `includes` string
- `startDate` string, date
- `endDate` string, date

## Response `200`

OK

- JobActionCollection — Base structure for all paginated collection responses. This provides consistent pagination metadata across all collection endpoints.
  - `count` integer — The total number of items available across all pages. Use this to calculate the total number of pages available.
  - `pageSize` integer — The number of items per page in this response. This reflects either your requested page size or the default value.
  - `pageStartIndex` integer — The starting index of this page of results. Use with pageSize to track your position in the overall result set.
  - `items` JobAction[]
    - `action` string — The action performed on this lead.
    - `type` 'Customer' | 'Job' | 'Lead' | 'Measurement' | 'Estimate' | 'Order' | 'Permit' | 'Payments' | 'Commission' | 'Precommission' | 'ContractWorksheet' | 'Supplement' | 'File' | 'Unspecified' | 'CommunicationHistory' | 'ContactNote' | 'JobContact' | 'Contact' | 'JobMessage' | 'ContractWorksheetStatus' | 'MortgageCheck' | 'Measurements' | 'Appointment' | 'JobEmail' | 'JobPacket' | 'Account' | 'Company' | 'User' | 'FeatureManager' | 'PermissionSettings' | 'LaborContact' | 'LaborOrder' | 'Financing' | 'JobSignatureEmail' | 'JobPaymentRequest' | 'TextMessage' — The type of action.
    - `date` string — Date and time the action happened represented in UTC.
    - `createdBy` CompanyUserLink
      - `id` string, uuid — The unique GUID of the AccuLynx User.
      - `_link` string — The unique URI of the AccuLynx User.

## Other responses

- `400` — Bad Request - The server cannot process the request due to a client error. Common causes: - Invalid request format - Missing required fields - Validation errors in the request data
- `401` — Unauthorized - Authentication is required or has failed. Common causes: - Missing API key - Invalid API key - Expired or deactivated API key
- `404` — Not Found - The requested resource does not exist. Common causes: - Invalid subscription ID - Subscription has been deleted - URL path contains typos or incorrect values
- `416` — Range Not Satisfiable - The requested page of results is not available. Common causes: - pageStartIndex is beyond the available data range - Invalid pagination parameters

---

[API](https://skmtc.net/acculynx/apis/acculynx-api-v2.md) · [All operations](https://skmtc.net/acculynx/apis/acculynx-api-v2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/acculynx/acculynx-api-v2/revisions/3a9e3886e400/schema)