---
title: "Get Jobs for a Contact"
method: GET
path: "/contacts/{contactId}/jobs"
tags: ["contacts"]
---

# Get Jobs for a Contact

`GET /contacts/{contactId}/jobs`

Retrieves a paginated list of all jobs that the contact is associated with.

**Pagination:**
- PageStartIndex: Zero-based index of the first record to return (default: 0)
- PageSize: Number of records per page (default: 25, max: 50)
- Both pagination parameters are optional

**Behavior:**
- Returns 200 with an empty items array if the contact exists but has no jobs associated
- Returns 400 if any path or a query string parameter (contactId, pageSize, pageStartIndex) doesn't fulfill the validations
- Returns 404 if the contactId does not exist
- Returns 416 if pageStartIndex or pageSize are negative, or exceeds the maximum allowed
- Returns 500 if an internal error occurs.

## Path parameters

- `contactId` string, uuid, required

## Query parameters

- `pageSize` integer
- `recordStartIndex` integer

## Response `200`

OK

- ContactJobCollection — 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` ContactJob[] — An array of jobs that the contact has been assigned to. Each item represents a job associated with the contact. The array may be empty if no jobs exist within the requested range.
    - `id` string, uuid — The job's unique ID.
    - `_link` string — The URI of this Job.

## 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
- `500` — Internal Server Error. The issue has been logged and will be reviewed as soon as possible.

---

[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)