Getting started

1. Create an account

Sign up at obzerv.xyz with email and password or Google. Free supports the dashboard walkthrough with HTTP and Ping monitors and email alerts.

2. Choose dashboard or API

The dashboard is available on every plan. Pro supports read-only API access; Business is required for the API write examples below. API keys do not bypass plan limits.

For API access, open Dashboard → API Keys → Generate Key. Copy the key from its one-time dialog and keep it in a secrets manager. It cannot be retrieved later.

export OBZERV_API_KEY="ug_live_..."

3. Create a monitor

In Dashboard → Add New Monitor, enter a friendly name and the full HTTP URL. Free supports check intervals of at least 3 minutes; Pro supports 30 seconds and Business supports 10 seconds. Choose All deployed regions for regional verification, or select a specific deployed region for a local check.

The API equivalent requires Business:

curl -X POST https://obzerv.xyz/api/monitors \
  -H "Authorization: Bearer $OBZERV_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Production API",
    "url": "https://api.example.com/health",
    "monitor_type": "http",
    "interval_seconds": 60,
    "regions": ["global"]
  }'

The monitor starts as pending. It receives a confirmed status after reliable observations arrive. Missing or inconclusive probe data may leave its current status unknown; it does not confirm an outage.

4. Configure alerts

Open Dashboard → Notifications → Add Channel. Email is available on Free, Slack/Discord/Telegram on Pro, and signed webhooks on Business.

For example, create a Slack channel through the API on Business:

curl -X POST https://obzerv.xyz/api/notification-channels \
  -H "Authorization: Bearer $OBZERV_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "slack",
    "name": "Engineering",
    "config": { "webhook_url": "https://hooks.slack.com/services/T00/B00/XXX" },
    "monitor_scope": "all"
  }'

An all scope receives events for current and future monitors. For a selected scope, supply monitor_scope: "selected" and monitor_ids; an empty selected list receives no monitor events. See notifications for subscriptions and Telegram setup.

5. Test delivery

Use Test notification on the channel, or the Business API:

curl -X POST "https://obzerv.xyz/api/notification-channels/<channel-id>" \
  -H "Authorization: Bearer $OBZERV_API_KEY"

A successful API response confirms the test request was accepted. Verify receipt at your destination too.

Next

• Monitor types — protocol configuration.
• Status pages — share confirmed service health.
• Webhook events — receive signed incident events.
• API reference — available endpoints.