---
title: "Get attached parts"
method: GET
path: "/v2/tasks/{taskID}/parts"
tags: ["Routes", "Tasks", "Parts"]
---

# Get attached parts

`GET /v2/tasks/{taskID}/parts`

Gets parts attached to a task.

This request gets parts associated with a task. A single Task can have multiple parts associated with it.

Return data description

Property: partID, Description: The partID of the part associated to this task.
Property: quantity, Description: The quantity of this part associated to this task.
Property: usedPrice, Description: The price of the part at the time of use.
Property: partName, Description: The name of the part.
Property: poItemID, Description: The unique ID of the PO item associated with this record.

## Response `200`

Get attached parts

- object[]
  - `partID` integer
  - `quantity` integer
  - `usedPrice` integer
  - `partName` string
  - `poItemID` 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.
- `404` — The referenced resource does not exist or is not visible to the authenticated customer.
- `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/versions/20801e23f7f2/schema)