---
title: "List WR Submissions"
method: GET
path: "/v2/work-requests/work-request-submissions"
tags: ["Routes", "Tasks", "Work Request Submissions"]
---

# List WR Submissions

`GET /v2/work-requests/work-request-submissions`

Lists WR submissions

Return data description:

| **Property** | **Description** |
| --- | --- |
| workRequestSubmissionId | The unique identifier of the work request submission. |
| status | Pending, Approved or Rejected. |
| createdByUserId | The unique identifier of the user who created the work request submission. |
| createdAt | The date the work request submission was created. The timestamp is in the following format: YYYY-MM-DD (2025-07-02) HH:MM:SS (21:36:31) |
| updatedAt | The date the work request submission was last updated. The timestamp is in the following format: YYYY-MM-DD (2025-07-02) HH:MM:SS (21:36:31) |
| deletedAt | The date the work request submission was deleted. The timestamp is in the following format: YYYY-MM-DD (2025-07-02) HH:MM:SS (21:36:31) Will be NULL if the submission is not deleted. |
| reviewedByUserId | The unique identifier of the user who reviewed the submission. |
| reviewedAt | The date the work request submission was reviewed. The timestamp is in the following format: YYYY-MM-DD (2025-07-02) HH:MM:SS (21:36:31) Will be NULL if the submission has not yet been reviewed |
| reviewedReason | The predefined reason the work request was declined. |
| additionalNotes | Any additional notes the person who declined the submission wishes to leave. |
| locationId | The unique identifier of the location the submission belongs to. |
| assetId | The unique identifier of the asset associated with the submission. |
| priorityId | The unique identifier of the priority of the submission. |
| dueDateUnit | The unit of measure used to communicate when the task will be due. Can be “days” or “hours”. |
| requestInformation | The information filled out in the Work Request Portal. Includes any of the following fields in JSON format. customerCode requesterName requesterEmail requesterPhone timeUnix customTag customFieldOne customFieldTwo customFieldThree customFieldOneTitle customFieldTwoTitle customFieldThreeTitle customFieldDropdownAnswerOne customFieldDropdownAnswerTwo customFieldDropdownAnswerThree customDropdownTitleOne customDropdownTitleTwo customDropdownTitleThree customDropdownOptionsOne customDropdownOptionsTwo customDropdownOptionsThree geoLocation |
| customerID | The unique identifier of the customer account. |
| requestTitle | The title of the submission. |
| assignedToProfileId | The Limble profile the submission is assigned to. This is used to determine what team or individual is assigned to review the submission. |
| requestDescription | The description of the problem filled out in the Work Request Portal. |
| checklistID | The unique identifier of the task generated from the submission when it is approved. Will be NULL if submission status is declined or pending. |
| requesterName | The name of the person who submitted the work request submission. |

## Query parameters

- `orderBy` string
- `search` string
- `locationIDs` integer
- `statuses` string
- `limit` integer
- `columns` string
- `createdDateStart` string
- `createdDateEnd` string
- `workRequestIDs` string
- `page` integer
- `cursor` integer

## Response `200`

List of work request submissions

- WorkRequestSubmission[]
  - `workRequestSubmissionId` integer
  - `status` 'Pending' | 'Approved' | 'Rejected'
  - `createdByUserId` integer
  - `createdAt` string
  - `updatedAt` string
  - `deletedAt` string, nullable
  - `reviewedByUserId` integer, nullable
  - `reviewedAt` string, nullable
  - `reviewedReason` string, nullable
  - `additionalNotes` string, nullable
  - `locationId` integer
  - `assetId` integer, nullable
  - `priorityId` integer, nullable
  - `dueDateUnit` string, nullable
  - `requestInformation` object
  - `customerID` integer
  - `requestTitle` string
  - `assignedToProfileId` integer, nullable
  - `requestDescription` string, nullable
  - `checklistID` integer, nullable
  - `requesterName` string

## Other responses

- `400` — The request was malformed — either invalid JSON syntax or a validation failure (missing required field, wrong type, etc.).
- `401` — No `Authorization` header was provided on the request.
- `403` — The supplied credentials are invalid, the customer account is inactive, or the credentials do not have permission to perform this action.
- `429` — The per-minute or per-hour rate limit for this credential and method has been exhausted. Inspect the `X-RateLimit-*` headers to determine when to retry.
- `500` — An unhandled server-side error. The body message is generic (`System unavailable...`) when the underlying cause is a database fault; otherwise it reflects the raised error.

---

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