---
title: "Get log entries"
method: GET
path: "/logs"
tags: ["logs"]
---

# Get log entries

`GET /logs`

Returns logs filtered by pipeline, driver, and runid

## Query parameters

- `pipeline` string
- `driver` string
- `runid` string

## Response `200`

List of logs

- TypesLog[]
  - `driver` string — Driver is the name of the driver that generated the log. This helps in identifying which component of the system produced the log.
  - `message` string — Message is the actual log message. This contains the information or error details that you want to record.
  - `pipeline` string — Pipeline is the name of the pipeline associated with the log. This allows you to trace logs back to specific pipelines.
  - `runid` string — RunID is a unique identifier for the workflow run. This allows you to group logs by specific runs of your pipelines.
  - `timestamp` string — Timestamp is the time when the log was created. This is useful for ordering logs and understanding the sequence of events.

## Other responses

- `500` — Internal server error

## Changes

- **2025-09-28** `ef1146f3d831` — 1 info
  - endpoint added
- **2025-08-17** `2bbb58594c86` — 1 breaking
  - api path removed without deprecation

[Change history](https://skmtc.dev/open-ug/apis/conveyor-ci-api/changes/logs/get.md)

---

[API](https://skmtc.dev/open-ug/apis/conveyor-ci-api.md) · [All operations](https://skmtc.dev/open-ug/apis/conveyor-ci-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/open-ug/conveyor-ci-api/revisions/4ad35de52cbb/schema)