---
title: "Vendor Logs"
method: GET
path: "/v2/vendors/{vendorID}/logs"
tags: ["Routes", "Vendors", "Logs"]
---

# Vendor Logs

`GET /v2/vendors/{vendorID}/logs`

This request returns the manual log entries for a vendor.

This request returns logs created manually by users on vendors. Logs related to tasks with vendors will not be returned.

**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.
vendorD | The ID of the vendor the log belongs to.
logEntry | The log entry for the vendor.
userID | The ID of the user that created the log.
logFiles | An array of objects that have a fileID, fileName and a link that can used to download the files attached to the log. All links are only valid for 15 minutes, a new call will generate a new link.

## Query parameters

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

## Response `200`

Vendor Logs

- LogEntry[]
  - `logID` integer
  - `dateCreated` integer
  - `logEntry` string
  - `userID` integer
  - `logFiles` object[]
    - `fileID` integer
    - `fileName` string
    - `link` string, uri

## 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)