Ship logs and metric data points, and manage HTTP, TCP, DNS, synthetic browser and page change monitors, programmatically with Lumen. Requests need a key with the monitoring:manage scope (or monitoring:*); a key without it gets 403 INSUFFICIENT_SCOPE.
Alert rules, notification channels, alerts and maintenance windows are on the Lumen alerting API page, and Space membership is on the Lumen Spaces API page.
Batch log ingestion. Submit up to 500 entries per request within a 256 KiB body limit.
curl -X POST https://projecthollow.com/lumen/ingest/v1/logs \
-H "Authorization: Bearer hlw_sk_…" \
-H "Content-Type: application/json" \
-d '{
"service": "checkout-api",
"entries": [
{ "level": "error", "message": "database connection timed out", "ts": "2026-10-05T08:00:00Z" }
]
}'Returns HTTP 202 Accepted: { "accepted": 1 }
Needs a key with the monitoring:ingest scope (or monitoring:manage or monitoring:*). Mint a key with only monitoring:ingest for a worker that ships telemetry: it can send logs and metrics and cannot do anything else in Lumen.
service is 1 to 100 characters of letters, digits and _ . : / @ + # ( ) - or space.ts is optional and defaults to the time the request arrives. When given it must be an ISO 8601 timestamp no more than 7 days old; one up to 5 minutes ahead is stored as the arrival time, and any other is skipped."rejected": { "count": n, "reasons": [...] } (the first five reasons); you only get HTTP 400 when no entry is valid.message is cut at 4,000 characters; level is info, warn or error.Batch metric ingestion. Submit up to 1,000 data points per request within a 256 KiB body limit.
curl -X POST https://projecthollow.com/lumen/ingest/v1/metrics \
-H "Authorization: Bearer hlw_sk_…" \
-H "Content-Type: application/json" \
-d '{
"service": "checkout-api",
"points": [
{ "name": "request_latency_ms", "value": 142, "ts": "2026-10-05T08:00:00Z", "tags": { "route": "/checkout" } }
]
}'Returns HTTP 202 Accepted: { "accepted": 1 }
Needs a key with the monitoring:ingest scope (or monitoring:manage or monitoring:*).
service follows the rules for logs; name is 1 to 128 characters from the same set. value must be a finite number.ts is optional and defaults to the time the request arrives. When given it must be an ISO 8601 timestamp no more than 7 days old; one up to 5 minutes ahead is stored as the arrival time, and any other is skipped."rejected": { "count": n, "reasons": [...] } (the first five reasons); you only get HTTP 400 when no point is valid.tags is a flat object of at most 20 entries: names up to 64 characters, values that are strings up to 256 characters, numbers, booleans or null, and no more than 4 KiB as JSON. A point with a nested value is skipped.Create or update a monitor as code: an http, tcp, dns, synthetic browser or page change check. Supply an Idempotency-Key header (or an idempotencyKey field in the body) to identify the monitor: the first call with a key creates it, and every later call with the same key applies the request to that same monitor.
curl -X POST https://projecthollow.com/lumen/ingest/v1/monitors \
-H "Authorization: Bearer hlw_sk_…" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: checkout-uptime-check" \
-d '{
"name": "Checkout API Uptime",
"type": "http",
"target": "https://checkout.example.com/health",
"intervalMinutes": 5,
"tags": ["prod", "checkout"],
"assertions": [{ "target": "status", "operator": "equals", "value": "200" }]
}'http, tcp, dns, browser or change.http(s) URL for http, browser and change; host:port for tcp (port 1 to 65535); a bare hostname for dns, with no scheme or spaces.1, 5, 15, 30 or 60. No other value is accepted.{"env": "prod"} is refused.prod, up to 24 characters, stored lowercase. all is reserved.browser monitors, ignored for the rest. See below.http monitors only; dropped for any other type. See below.change monitors only. { "region", "intent" }: a region of { "kind": "selector", "selector" } (up to 300 characters) or { "kind": "text", "startText", "endText" } (up to 200 characters each) limits what is watched, and an intent (plain English, up to 500 characters) says which changes matter. Over-long values are refused, not cut.taskListId. Send it with taskListId; it is refused on its own.taskSpaceId. On its own it is looked up across your Spaces: a list id found in exactly one of them is used with that Space, and one found in none, or in more than one, is refused with 400 INVALID_REQUEST (send taskSpaceId to choose).A browser monitor needs a steps array of 1 to 20 steps. Each step has a kind (click, fill, wait_for or assert_text), a DOM selector string, a text value (required for fill and assert_text), and an optional timeoutMs. A step that sets no timeoutMs waits up to 5,000 ms, and a larger value is capped at 15,000 ms.
An http monitor can check more than the status code. Send up to 10 assertions, each { "target", "operator", "value" }. The target is status, header, json_path, body or duration, and the operator is equals, contains, regex, less_than or greater_than. The header and json_path targets also need headerName: the header to read, or the JSON path to evaluate. less_than and greater_than need a numeric value.
"assertions": [
{ "target": "status", "operator": "equals", "value": "200" },
{ "target": "header", "operator": "contains", "headerName": "content-type", "value": "json" },
{ "target": "duration", "operator": "less_than", "value": "800" }
]{ "id": "mon_123" } for a new monitor.{ "id": "mon_123", "duplicate": true } when the key matched an earlier create. The monitor was updated with this request.MISSING_IDEMPOTENCY_KEY when no key was sent, or INVALID_REQUEST for a field that fails validation, on a create and an update alike.RESOURCE_LIMIT_EXCEEDED when you already have as many monitors as your plan allows.An update replaces the whole definition: a field left out of the request is cleared (tags, env, assertions, changeWatch, taskSpaceId, taskListId, spaceId), and leaving out paused resumes a paused monitor. Send the complete monitor every time. Lumen remembers an idempotency key for 30 days from the call that created the monitor; after that, the same key creates a new monitor.
Fetch every monitor you own, paused ones included, plus every monitor shared into a Space you belong to, sorted by name. status is pending, up, down, degraded or paused, and spaceId appears only on a monitor shared into a Space.
{
"monitors": [
{ "id": "mon_123", "name": "Checkout API Uptime", "type": "http", "target": "https://checkout.example.com/health", "status": "up", "intervalMinutes": 5 }
]
}Retrieve status details and timestamp for a specific monitor instance.
{ "id": "mon_123", "status": "up", "lastCheckedAt": "2026-07-31T08:00:00Z" }Delete a monitor and its stored screenshots. Returns { "ok": true } whether or not the monitor still existed, so a retried delete is safe. A monitor shared into a Space can be deleted by the Space's owner or an admin, not by a plain member.
curl -X DELETE https://projecthollow.com/lumen/ingest/v1/monitors/mon_123 \ -H "Authorization: Bearer hlw_sk_…"