--- title: "Tasks" method: GET path: "/v2/tasks" tags: ["Routes", "Tasks"] --- # Tasks `GET /v2/tasks` This request gets top level information about Tasks such as completed date, assignment, assetID, etc. **Note:** this endpoint supports pagination. Please refer to the [Pagination](#pagination) section for more information. Return data description meta | This property has shortcuts to get other information related to the Task such as the Task's invoices, labor parts usage and instructions. name | The Task's name. userID | The id of the user this Task is assigned to. A Task can not be assigned to both a Team and a User at the same time. teamID | The id of the team this Task is assigned to. A Task can not be assigned to both a Team and a User at the same time. locationID | The id of the Location in which this Task belongs to. template | This field indicates if the task is a 'template' that spawns other tasks based on schedules or not. createdDate | The date this Task was created. This is a unix timestamp. startDate | By default this value is 0 as the startDate is usually the same as the createdDate. Sometimes a task is created such that it is scheduled to start in the future (i.e. after the createdDate). In such a case this value will be a unix timestamp indicating the actual start date of the Task. scheduledStart | The scheduled start date of the Task. This is a unix timestamp. A value of null means no scheduled start date is set. scheduledEnd | The scheduled end date of the Task. This is a unix timestamp. A value of null means no scheduled end date is set. due | The date this Task is due. This is a unix timestamp. dateCompleted | The date this Task was completed. This is a unix timestamp. A value of 0 means this Task is not completed. lastEdited | The date this Task was last edited. This is a unix timestamp. description | The decription of a task. completedByUser | The id of the User that completed this Task. lastEditedByUser | The id of the User that last edited the task. assetID | The id of the Asset that this Task belongs to. completedUserWage | The price per hour of the User's Wage at the point in time when the task was completed. priority | The priority of the Task. downtime | The amount of downtime in seconds caused by this Task. estimatedTime | The estimated time of the task. This is the time it takes to complete the task in minutes. completionNotes | Notes inputted by the user at the time of task completion. requestorName | The name of the person that requested this Task. requestorEmail | The email of the person that requested this Task. requestorPhone | The phone number of the person that requested this Task. requestTile | The title of the work request being submitted. requestField1 | Work request portal custom field 1. requestField2 | Work request portal custom field 2. requestField3 | Work request portal custom field 3. requestDropdown1 | Work request portal custom dropdown box 1. requestDropdown2 | Work request portal custom dropdown box 2. requestDropdown3 | Work request portal custom dropdown box 3. requestorDescription | The description of the request submitted via the Work Request portal. type | 1 = Preventative Maintanance (PM);, 2 = Unplanned Work Order (WO);, 4 = Planned Work Order (WO);, 5 = Cycle Count;, 6 = Work Request (WR);, 7 = Min Part Threshold;, 8 = Materials Request; status | 1 - Complete, 0 - Incomplete, Note: this property indicates a task status with respect to task completion. For the custom task status refer to statusID statusID | The current custom status assigned to this task., Note: this indicates the current status of a task. Use GET Statuses to find the value of each statusID. poIDs | An array of Purchase Order IDs linked to this Task. Returns an empty array if no Purchase Orders are linked. associatedTaskID (deprecated) | Please refer to associatedTask meta property on GET Task Instruction for instruction type 14. meta1 | Task meta data. This does not show in the web application, but can be used to track items between integrated systems. meta2 | Task meta data. This does not show in the web application, but can be used to track items between integrated systems. meta3 | Task meta data. This does not show in the web application, but can be used to track items between integrated systems. geoLocation | The location of a task on a Map. customTags | An array of custom tags associated with the task. ## Query parameters - `tasks` integer - `assets` integer - `locations` integer - `type` integer - `name` string - `start` integer - `end` integer - `cursor` integer - `limit` integer - `page` integer - `completedStart` integer - `completedEnd` integer - `scheduledStart` integer - `scheduledEnd` integer - `orderBy` string - `geoLocation` boolean - `users` integer - `teams` integer - `lastEditedByUsers` string - `status` integer - `meta1` integer - `meta2` integer - `meta3` integer - `statusIDs` string - `tag` string ## Response `200` Pagination using Page & Limit - Task[] - `meta` object - `invoices` string - `labor` string - `partsUsage` string - `instructions` string - `status` string - `taskID` integer - `poIDs` integer[] - `name` string - `userID` integer - `teamID` integer - `locationID` integer - `template` boolean - `createdDate` integer - `scheduledStart` integer - `scheduledEnd` integer - `due` integer - `description` string - `dateCompleted` integer - `lastEdited` integer - `lastEditedByUser` integer - `completedByUser` integer - `assetID` integer - `completedUserWage` integer - `priority` integer - `priorityID` integer - `downtime` integer - `completionNotes` unknown - `requestorName` unknown - `requestorEmail` unknown - `requestorPhone` unknown - `requestTitle` unknown - `requestField1` unknown - `requestField2` unknown - `requestField3` unknown - `requestDropdown1` unknown - `requestDropdown2` unknown - `requestDropdown3` unknown - `requestorDescription` unknown - `meta1` unknown - `meta2` unknown - `meta3` unknown - `statusID` integer - `type` integer - `status` integer ## 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)