Skip to main content

Overview

The Kener API v4 lets you programmatically manage every resource in your status page: monitors, incidents, maintenances, pages, and site settings. All endpoints accept and return JSON. Base URL
/api/v4

Authentication

All API endpoints require a valid API key passed as a Bearer token. See the Authentication page for details.

Request format

  • Set Content-Type: application/json on all requests with a body.
  • Timestamps are UTC Unix timestamps in seconds (integer). All timestamps are automatically truncated to the start of the minute.

Response format

Successful responses return the requested or mutated resource directly in the JSON body. Error responses follow a consistent shape:
{
  "error": {
    "code": "ERROR_CODE",
    "message": "Human-readable description."
  }
}

HTTP status codes

StatusMeaning
200Request succeeded.
201Resource created successfully.
400Bad request — missing or invalid parameters.
401Unauthorized — missing or invalid API key.
404Resource not found.
500Internal server error.

Error codes

CodeDescription
BAD_REQUESTValidation failed or required fields are missing.
UNAUTHORIZEDAPI key is missing or invalid.
NOT_FOUNDThe requested resource does not exist.
INTERNAL_ERRORAn unexpected server-side error occurred.

Pagination

The maintenance events list endpoints support cursor-style pagination via page and limit query parameters.
ParameterDefaultMaxDescription
page1Page number (1-indexed).
limit20100Number of results per page.
Paginated responses include page, limit, and (where available) total fields at the top level of the response object.

Available resources

Monitors

Create, read, update monitors. Push and query monitoring data points.

Incidents

Manage incidents and add timeline comments.

Maintenances

Schedule recurring or one-time maintenance windows and manage their events.

Pages

Create and configure status pages and their monitor lists.

Site

Read and update global site configuration keys.

Build docs developers (and LLMs) love