Skip to main content
GET
List a monitor's runs
List a monitor’s runs, newest first. Each completed run carries the pages it returned in results.

When to use it

Read the run history to catch up on digests you missed, or to find failed runs: a failed run has status failed and says why in error. Its pages aren’t lost. They come with the next run that succeeds. Pages and pagination work as in List monitors: pass next_cursor as cursor for the next page. A run returns at most search.max_results pages. For every page the monitor accepted, including those past that cap, use List results.

SDK, CLI and MCP

The SDK methods need SDK 0.2.0 or later. See SDKs → Monitors and CLI → Monitors. See Read the results of a run.

Authorizations

X-API-Key
string
header
required

Your API key, such as keen_.... Create one in the Keenable console. If you send both this header and Authorization, the API uses this one.

Path Parameters

id
string
required

The monitor's ID, such as mon_3kq9z2c8f1a04b7d9e6f5a21.

Query Parameters

limit
integer
default:50

Items per page, 1 to 100. Any other value returns 400.

Required range: 1 <= x <= 100
cursor
string

The next_cursor of the previous page. A cursor that isn't in the list returns 400.

Response

A page of runs

data
object[]
required
has_more
boolean
required

true if there are more items after this page.

next_cursor
string | null
required

Pass it as cursor to get the next page. null on the last page.