Skip to main content
GET
TypeScript
List the monitor’s results, every page it accepted, newest first, whether or not a run or webhook delivered it. To read a monitor without a webhook or schedule, poll this endpoint and stop at the first id you’ve already seen.

When to use it

Use it when you have no public endpoint for a webhook and no schedule, or to look back over results a run or webhook already gave you. Pass min_importance=4 to keep only the results not to be missed. This request returns them:
Replace mon_123 with your monitor’s id. You get the results in data, newest first. Each one has a summary, an importance from 1 to 5, and same_story, the number of pages on the same story that were left out. Store the first id and stop at it on the next poll. An empty data on a new monitor is expected: it matches only pages crawled after it was created.

SDK, CLI and MCP

The SDK methods need SDK 0.2.0 or later. See SDKs → Monitors, CLI → Monitors and Monitors tools. Read monitor results shows the polling loop.

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

min_importance
integer

Only results rated at least this important. 4 keeps the results a reader wouldn't want to miss.

Required range: 1 <= x <= 5
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 results

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.