Events

The project-wide routing grid

Returns one row per (check, event_type) pair that has ever been routed — the same rows GET /api/v1/checks/{id}/routes would return for each check individually, gathered project-wide in one call so a caller does not have to walk every monitor to render a routing matrix.

Ordered by check name, then event type, for a stable grid. Not paginated — the row count is bounded by monitors × event types (at most 8 event types per check today), not by unbounded user activity, so a single response is always the complete answer.

This endpoint is read-only. Edit a route through the existing PUT/DELETE /api/v1/checks/{id}/routes/{event_type}.

Console stability note. This response is shaped by a console screen: the fields are the ones that screen draws, in the grouping it draws them in. It stays published because reading it is a reasonable thing to automate, and no field will be removed or change meaning without a version. Fields may be ADDED as the screen grows, so treat unknown keys as normal rather than as an error.

get/api/v1/routes

Request

Base URL: https://app.lastping.dev
URL: https://app.lastping.dev/api/v1/routes
Auth: API key in header X-Api-Key

Response

The full routing grid (may be empty).

Example response

{
  "routes": [
    {
      "check_id": "550e8400-e29b-41d4-a716-446655440000",
      "check_name": "Nightly backup",
      "event_type": "down"
    }
  ]
}

Changes

No recorded changes to this operation across all 2 revisions of this API.