Logging API: send logs, heartbeats and monitors to one endpoint

Headers

Content-Type: application/json

Body (JSON)

Monitor types

Monitor status (color)

The optional monitor_status field controls the color tint of the monitor card on the dashboard. It is independent of the log status field.

When omitted, the monitor card renders with a neutral appearance.

Example: sending a monitor

curl -X POST https://app.logblazer.com/api/logs/YOUR_API_KEY \
  -H "Content-Type: application/json" \
  -d '{
    "payload": "Health check passed",
    "status": "SUCCESS",
    "source": "health-checker",
    "monitor_title": "API Status",
    "monitor_type": "status",
    "monitor_value": "healthy",
    "monitor_status": "success",
    "monitor_meta": "42 ms"
  }'

201 Created

{
  "message": "Log received"
}

404 Not Found

Returned when the API key does not match any project.

422 Unprocessable Entity

Returned when validation fails (e.g. missing payload or invalid status value).

cURL

curl -X POST https://app.logblazer.com/api/logs/YOUR_API_KEY \
  -H "Content-Type: application/json" \
  -d '{"payload": "User signed up", "status": "SUCCESS", "source": "auth-service"}'

JavaScript (fetch)

await fetch("https://app.logblazer.com/api/logs/YOUR_API_KEY", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    payload: "Deployment finished",
    status: "SUCCESS",
    source: "deploy-script"
  })
});

PHP

$response = Http::post("https://app.logblazer.com/api/logs/YOUR_API_KEY", [
    'payload' => 'Database backup completed',
    'status'  => 'SUCCESS',
    'source'  => 'backup-worker',
]);

Python

import requests

requests.post("https://app.logblazer.com/api/logs/YOUR_API_KEY", json={
    "payload": "Cron job failed: timeout after 30s",
    "status": "FAILURE",
    "source": "cron-worker"
})

Bash (minimal)

# Minimum required — just the payload
curl -X POST https://app.logblazer.com/api/logs/YOUR_API_KEY \
  -H "Content-Type: application/json" \
  -d '{"payload": "Something happened"}'

Response

Returns text/plain Markdown with monitors table and recent log entries. No authentication required.

# My Project — Dashboard

Generated: 2026-03-05 14:30:00 UTC

## Monitors (2)

| Monitor | Value | Monitor Status | Updated |
|---|---|---|---|
| API Status | healthy | success | 2026-03-05 14:25:00 |
| Deploy | DEPLOYED | success | 2026-03-05 14:20:00 |

## Recent Logs (3)

| Time | Source | Status | Payload |
|---|---|---|---|
| 2026-03-05 14:25:00 | health-checker | SUCCESS | Health check passed |
| 2026-03-05 14:20:00 | deploy-pipeline | SUCCESS | Production deployed |
| 2026-03-05 14:15:00 | cron | NOTICE | Backup completed |

Usage

curl https://app.logblazer.com/d/YOUR_API_KEY/llm

Use this endpoint to give AI agents and LLMs access to your project's current status. The same public dashboard is also available as a web page at /d/{api_key}.

Register a heartbeat

{
  "id": "uuid",
  "name": "My App Production",
  "short_name": null,
  "url": "https://myapp.com/api/heartbeat",
  "interval_minutes": 3,
  "timeout_seconds": 10,
  "alert_emails": ["ops@myapp.com"],
  "alert_after_failures": 2,
  "is_active": true,
  "last_status": "UNKNOWN",
  "created_at": "2026-03-09T12:00:00Z"
}

Other heartbeat endpoints

Expected response

{
  "status": "PASS",
  "checks": {
    "database": {
      "status": "PASS",
      "ms": 3,
      "detail": "SELECT 1 succeeded",
      "label": "DB Connection"
    },
    "queue_health": {
      "status": "PASS",
      "detail": "No stale jobs"
    },
    "external_api": {
      "status": "FAIL",
      "ms": 5023,
      "detail": "Timeout after 5s"
    }
  }
}

HTTP status codes

Return 200 when all checks pass and 503 when one or more checks fail. Any other status code, timeout, or connection error is treated as a complete failure.

Example: registering and checking a heartbeat

# Register a heartbeat
curl -X POST https://app.logblazer.com/api/heartbeats/YOUR_API_KEY \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Production API",
    "url": "https://myapp.com/api/heartbeat",
    "interval_minutes": 5,
    "alert_emails": ["ops@myapp.com"],
    "alert_after_failures": 3
  }'

# Check status
curl https://app.logblazer.com/api/heartbeats/YOUR_API_KEY/HEARTBEAT_ID/status

# Trigger an immediate check
curl -X POST https://app.logblazer.com/api/heartbeats/YOUR_API_KEY/HEARTBEAT_ID/check

How it works

Pass and fail selectors

A browser check does not decide health from the HTTP status alone. Once the page has loaded, LogBlazer polls the rendered DOM — every frame on the page, not just the top document — until one of your selectors matches a visible element or the render budget runs out.

Order of evaluation for one check: a page that fails to load is a FAIL; an HTTP status outside 200–299 is a FAIL recorded without evaluating any selector; otherwise LogBlazer polls fail selectors then pass selectors, roughly ten times a second, until render_timeout_seconds elapses. Nothing matching by then is a FAIL with reason render_timeout.

Create a browser monitor

* These fields have server-side defaults. Omit the key to take the default, or send a value — but an explicit null is rejected with a 422 rather than falling back to the default.

{
  "browser_monitor": {
    "id": "uuid",
    "project_id": "uuid",
    "name": "Marketing Site",
    "short_name": "mkt",
    "url": "https://myapp.com/pricing",
    "interval_minutes": 15,
    "render_timeout_seconds": 45,
    "alert_emails": ["ops@myapp.com"],
    "alert_after_failures": 3,
    "consecutive_failures": 0,
    "last_checked_at": null,
    "last_status": "UNKNOWN",
    "is_active": true,
    "created_at": "2026-03-09T12:00:00Z",
    "updated_at": "2026-03-09T12:00:00Z",
    "is_stale": false,
    "selectors": [
      {
        "id": "uuid",
        "browser_monitor_id": "uuid",
        "selector": "#pricing-table",
        "kind": "pass",
        "label": "Pricing table",
        "position": 0,
        "created_at": "2026-03-09T12:00:00Z",
        "updated_at": "2026-03-09T12:00:00Z"
      },
      {
        "id": "uuid",
        "browser_monitor_id": "uuid",
        "selector": ".error-banner",
        "kind": "fail",
        "label": "Error banner",
        "position": 1,
        "created_at": "2026-03-09T12:00:00Z",
        "updated_at": "2026-03-09T12:00:00Z"
      }
    ],
    "latest_result": null
  }
}

Other browser monitor endpoints

Every response other than the delete returns the monitor wrapped in a browser_monitor key; the list endpoint wraps its array in browser_monitors. A PATCH is a true partial update: omitted fields are left alone. selectors is the exception — supply it and it replaces the entire set, so selector ids are not stable across an update, and the replacement must still contain at least one pass selector. Omit selectors to leave them untouched.

Check results

Every check writes a result row. The status endpoint returns three keys — browser_monitor with its selectors, latest_result, and recent_results (up to 100, newest first). The list, create, update, and check responses embed the newest one as latest_result, which is null until a check has run.

{
  "id": "uuid",
  "browser_monitor_id": "uuid",
  "status": "FAIL",
  "error_reason": "fail_selector_matched",
  "status_code": 200,
  "matched_selector_id": "uuid",
  "matched_frame_url": "https://myapp.com/pricing",
  "duration_ms": 2318,
  "console_errors": ["TypeError: undefined is not a function"],
  "network_failures": [
    { "url": "https://myapp.com/api/plans", "status": 500, "method": "GET" }
  ],
  "screenshot_path": "browser-monitor-screenshots/uuid/uuid.png",
  "error_message": null,
  "created_at": "2026-03-09T12:00:00Z"
}

Failure reasons

Example: creating and checking a browser monitor

# Create a browser monitor
curl -X POST https://app.logblazer.com/api/browser-monitors/YOUR_API_KEY \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Marketing Site",
    "url": "https://myapp.com/pricing",
    "interval_minutes": 15,
    "render_timeout_seconds": 45,
    "alert_emails": ["ops@myapp.com"],
    "alert_after_failures": 3,
    "selectors": [
      { "selector": "#pricing-table", "kind": "pass", "label": "Pricing table" },
      { "selector": ".plan-card", "kind": "pass" },
      { "selector": ".error-banner", "kind": "fail", "label": "Error banner" }
    ]
  }'

# Read current status, latest result, and recent results
curl https://app.logblazer.com/api/browser-monitors/YOUR_API_KEY/MONITOR_ID/status

# Queue an immediate check
curl -X POST https://app.logblazer.com/api/browser-monitors/YOUR_API_KEY/MONITOR_ID/check

How it works