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 URLAuthentication
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/jsonon 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:HTTP status codes
| Status | Meaning |
|---|---|
200 | Request succeeded. |
201 | Resource created successfully. |
400 | Bad request — missing or invalid parameters. |
401 | Unauthorized — missing or invalid API key. |
404 | Resource not found. |
500 | Internal server error. |
Error codes
| Code | Description |
|---|---|
BAD_REQUEST | Validation failed or required fields are missing. |
UNAUTHORIZED | API key is missing or invalid. |
NOT_FOUND | The requested resource does not exist. |
INTERNAL_ERROR | An unexpected server-side error occurred. |
Pagination
The maintenance events list endpoints support cursor-style pagination viapage and limit query parameters.
| Parameter | Default | Max | Description |
|---|---|---|---|
page | 1 | — | Page number (1-indexed). |
limit | 20 | 100 | Number of results per page. |
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.