Skip to main content

Documentation

Complete guide to setting up website monitoring with PingZen. API documentation, code examples, and best practices.

Alert Configuration

PingZen supports multiple alert channels. Configure one or more channels for redundancy.

Telegram

The fastest way to receive notifications (1-2 seconds). One-click setup.

  1. 1.In PingZen go to Alerts → Create Alert → select Telegram
  2. 2.Click 'Connect Telegram' — a link to @pingzen_bot opens automatically
  3. 3.Press Start in Telegram — your account is linked instantly
  4. 4.For group alerts: switch to 'Group Chat' tab and click 'Add Bot to Group'

No need to copy Chat IDs manually — the wizard handles everything. You can also enter a Chat ID manually if needed.

Slack

Integration via Incoming Webhooks for team collaboration.

  1. 1.In Slack go to Settings → Apps → Incoming Webhooks
  2. 2.Click 'Add New Webhook to Workspace'
  3. 3.Select a channel for notifications
  4. 4.Copy the Webhook URL (https://hooks.slack.com/...)
  5. 5.In PingZen create an alert and paste the URL

Create a dedicated #alerts channel for monitoring notifications.

Discord

One-click OAuth setup or paste a Webhook URL.

  1. 1.In PingZen go to Alerts → Create Alert → select Discord
  2. 2.Click 'Connect Discord' — you'll be redirected to Discord
  3. 3.Select your server and channel, then authorize
  4. 4.You're redirected back — the webhook is saved automatically

You can also paste a Webhook URL manually if you prefer. Create it in Discord: Server Settings → Integrations → Webhooks.

Microsoft Teams

Send alerts to Microsoft Teams channels via Incoming Webhook.

  1. 1.In Teams select channel → More options → Connectors
  2. 2.Find 'Incoming Webhook' and click Configure
  3. 3.Name the webhook and copy the URL
  4. 4.In PingZen create an MS Teams alert
  5. 5.Paste the Webhook URL

Mattermost

Slack-compatible webhooks for self-hosted teams.

  1. 1.In Mattermost: Main Menu → Integrations → Incoming Webhooks
  2. 2.Click Add Incoming Webhook
  3. 3.Select a channel and copy the Webhook URL
  4. 4.In PingZen use the Mattermost type

WhatsApp

Receive alerts via WhatsApp through the Twilio API.

  1. 1.Create a Twilio account and set up a WhatsApp Business API
  2. 2.Get your Twilio Account SID, Auth Token, and WhatsApp number
  3. 3.In PingZen create a WhatsApp alert
  4. 4.Enter your WhatsApp phone number (with country code, e.g. +1234567890)

WhatsApp alerts require a Twilio account with WhatsApp Business API enabled.

PagerDuty

Route alerts to PagerDuty for on-call escalation.

  1. 1.In PagerDuty go to Services → Service Directory → select your service
  2. 2.Go to Integrations tab → Add Integration → Events API v2
  3. 3.Copy the Integration Key (routing key)
  4. 4.In PingZen create a PagerDuty alert and paste the routing key

PagerDuty triggers real incidents with escalation policies — ideal for production services.

Browser Push Notifications

Get instant push notifications directly in your browser — no apps or extensions needed.

  1. 1.Go to Settings → Notifications in PingZen
  2. 2.Click 'Enable Push Notifications'
  3. 3.Allow notifications when your browser prompts
  4. 4.Alerts will be delivered even when PingZen is not open

Browser push works on Chrome, Firefox, and Edge. Requires HTTPS.

Webhook

Send JSON data to your HTTP endpoint for custom integrations.

  1. 1.Create an HTTP endpoint on your server to receive POST requests
  2. 2.In PingZen create a Webhook alert
  3. 3.Enter your endpoint URL
  4. 4.Optionally add authentication headers

JSON Payload Format

{
  "text": "🔴 My Website - DOWN",
  "body": "URL: https://example.com\nProtocol: HTTPS\nResponse time: 5000 ms\nError: Connection timeout",
  "priority": "critical",
  "timestamp": "2026-03-18T10:30:00+00:00",
  "source": "pingzen"
}

Alert Triggers

Choose which events should send notifications:

DOWN

Service Down (DOWN)

Sent when a monitor transitions to DOWN status after confirmation (default: 3 consecutive failures).

UP

Recovery (RECOVERED)

Sent when a monitor recovers after being down.

DEGRADED

Degradation (DEGRADED)

Sent when service is degraded (incl. PageSpeed score below threshold).

SSL

SSL Expiring

Sent 14 days before SSL certificate expiration.

Message Settings

Customize which information is included in alert notifications. By default most fields are enabled. You can toggle each field per alert.

✓URL — the monitored endpoint address
✓Protocol — HTTP, TCP, DNS, etc.
✓Response time — check duration in milliseconds
✓HTTP status code — response status (e.g. 200, 502)
✓Error message — failure details or timeout reason
—Account info — your email or account name (disabled by default for privacy)
✓Downtime duration — how long the monitor was down (shown only on recovery)
✓Monitor link — clickable link to open the monitor page in PingZen

Disable fields you don't need to keep notifications concise. The 'Account info' field is disabled by default for privacy.

Heartbeat Monitor Alerts

Alerts work with both regular monitors and heartbeat monitors. When creating an alert, you can select heartbeat monitors in the 'Heartbeat Monitors' section below the regular monitor list.

One alert can watch both regular and heartbeat monitors at the same time. The monitor count shows the total of both types.

Reminder Alerts

Enable the 'Send reminders while down' toggle to receive periodic notifications while a monitor stays down. Reminder intervals escalate automatically: 5 min → 15 min → 1 hour → then every 4 hours. The schedule resets when the monitor recovers.

Reminders are disabled by default. Enable them for critical services where you need persistent escalation.

Cooldown Period

Minimum time between repeated alerts for the same issue. Prevents notification spam during unstable connections. Default: 5 minutes. Recovery alerts always bypass cooldown.

Recommended: 5-15 minutes for production environments.

Alert History

The 'History' tab on the Alerts page shows a log of all sent notifications: timestamp, trigger type, channel, target, and delivery status (sent/failed). Failed deliveries include error details.

Use alert history to verify that notifications are being delivered correctly and to diagnose delivery failures.

Alerts API

Manage alerts programmatically via REST API.

GET/api/v1/alerts

List Alerts

POST/api/v1/alerts

Create Alert

PATCH/api/v1/alerts/:id

Update Alert

DELETE/api/v1/alerts/:id

Delete Alert

POST/api/v1/alerts/:id/test

Test Alert

Common Questions

What protocols can I monitor?

PingZen supports 23 protocols: HTTP/HTTPS, WebSocket (WS/WSS), TCP, UDP, ICMP Ping, gRPC, DNS, WHOIS, SSL certificates, Email (SMTP/IMAP/POP3), FTP/FTPS, DNSBL, PageSpeed, SOCKS5, MTProxy, API Check, and Transaction. You can monitor websites, APIs, servers, databases, and any network service.

How fast can I get alerts?

Telegram alerts are delivered within 1-2 seconds of detection. Slack and Discord notifications arrive almost instantly. You can configure multiple alert channels for redundancy.

Can I organize monitors by project?

Yes! PingZen supports workspaces, which let you organize monitors by project, environment, or team. Each workspace can have its own alert configurations and team members.

Is there an API for automation?

Absolutely. PingZen provides a full REST API with OpenAPI documentation. You can create, update, and delete monitors programmatically.

How do status pages work?

Status pages are public, branded pages showing your services' uptime. You can display real-time status and allow customers to subscribe for updates.

What happens if I reach my monitor limit?

We'll notify you when approaching your limit. You can pause some monitors or contact us for increased capacity. We never stop monitoring without warning, ensuring your critical services stay protected.

Ready to stop missing downtime?

Join thousands of teams who trust PingZen. Setup takes 30 seconds.

Start Free