---
title: "Part Logs"
method: GET
path: "/v2/parts/{partID}/logs"
tags: ["Routes", "Parts", "Logs"]
---

# Part Logs

`GET /v2/parts/{partID}/logs`

This request returns the log entries for a part.

**Note:** this endpoint supports pagination. Please refer to the [Pagination](#pagination) section for more information.

Return data description

logID | The unique logID of the log.
dateCreated | The date the log was created as a UNIX timestamp.
partID | The partID the log belongs to.
sourceID | The sourceID of the source of the log. The sourceID can be as follows:, 1: Part name was changed., 2: Part Number was changed., 3: Parts were added/removed., 4: Manual log entry., 5: Parts were used on a Task., 6: Part Price was changed., 7: Stale threshold was manually changed., 8: Part Qty threshold was manually changed., 11: Part Qty threshold status was changed., 13: Part Location was changed., 14: Part Vendor was changed., 15: Part Image was changed., 18: Parts were received on a Bill., 19: Part Maximum Part Qty was manually changed., 20: Some of a PO Item Received Qty was used during manual Part Qty adjustment
logEntry | The log entry for the part.
userID | The ID of the user that created the log.
associatedID | The ID of the item associated with this log, if any. Current examples include:, sourceID: 5, associatedID type: Task, sourceID: 18, associatedID type: Bill, sourceID: 20, associatedID type: Bill

## Query parameters

- `logs` integer
- `sources` integer
- `users` integer
- `logEntry` string
- `start` integer
- `end` integer
- `page` integer
- `limit` integer
- `cursor` string

## Response `200`

Part Logs

- PartLogEntry[]
  - `logID` integer
  - `dateCreated` integer
  - `partID` integer
  - `sourceID` integer
  - `logEntry` string
  - `userID` integer
  - `associatedID` 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)