---
title: "Fetch a list of Live query campaigns"
method: GET
path: "/live_queries"
---

# Fetch a list of Live query campaigns

`GET /live_queries`

## Query parameters

- `cursor` string
- `per_page` integer
- `search` string

## Response `200`

A paged array of Live query campaigns

- object
  - `page` integer — current page of data, as specified by the 'page' request parameter. This page number is 0-indexed.
  - `last_page` integer — the final page number for the dataset. This is zero-indexed, so that a dataset with a record count less than or equal to the page size will be 0.
  - `data` LiveQueryCampaign[] — Details about the Live query campaigns
    - `id` string — The canonical identifier for this live query campaign
    - `osquery_sql` string — The sql to be run on all targeted devices
    - `name` string — The title of the live query
    - `created_at` string, date-time — The creation timestamp of the live query campaign
    - `published` boolean — Describes whether or not the author of the LQ has published the live query (true) or if it is still a draft (false)
    - `revision` integer — Editing a Live Query results in it's revision being incremented. When the live query's revision is incremented, it causes the live query to be re-run on all target devices
    - `successful_devices_count` integer — The number of device that have successfully run the query
    - `errored_devices_count` integer — The number of device that returned an error when attempting to run the query
    - `waiting_devices_count` integer — The number of device that have not yet reported results or errors running the device
    - `tables_used` string — The names of the tables referenced in the osquery SQL
    - `author` object — The user who authored this live query campaign
      - `id` string — The canonical identifier for this user
      - `name` string — The human-readable name for this user
      - `email` string — the recorded email address for this user
      - `created_at` string, date-time — when the user accepted their invite and finished creating their Kolide account

## Other responses

- `403` — An 'unauthorized' response may occur for features restricted by or unavailable to your organization

---

[API](https://skmtc.net/kolide/apis/k2-api.md) · [All operations](https://skmtc.net/kolide/apis/k2-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/kolide/k2-api/versions/7013d788398e/schema)