---
title: "Parts Usage"
method: GET
path: "/v2/parts/usage"
tags: ["Routes", "Parts"]
---

# Parts Usage

`GET /v2/parts/usage`

This request gets your Parts usage log.

Return data description

Property: meta, Description: A call which can be used to quickly look up the Task that this part's usage was recorded on.
Property: name, Description: The name of the part used.
Property: taskID, Description: The associated Task where this part was used.
Property: usedCount, Description: The number of parts that were used.
Property: usedPrice, Description: The price per 1 part.
Property: usedOn, Description: The date when the part was used. This is a unix timestamp.
Property: poItemID, Description: The unique ID of the PO item associated with this usage record.

## Query parameters

- `parts` integer
- `tasks` string
- `start` integer
- `end` integer
- `name` string
- `cursor` integer
- `limit` integer

## Response `200`

Parts Usage

- object[]
  - `meta` object
    - `task` string
    - `part` string
  - `partID` integer
  - `name` string
  - `taskID` integer
  - `usedCount` integer
  - `usedPrice` integer
  - `usedOn` integer
  - `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.
- `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)