Xitoring Document
Home
FAQ
Support
Register
Home
FAQ
Support
Register
  • Xitoring

    • Introduction
    • Release Notes
    • Xitoring Release Notes
    • Linux Xitogent Release Notes
    • Windows Xitogent Release Notes
    • Xitoring Mobile App Release Notes
    • Account Management
    • API Access & Automation
    • Team Management & Collaboration
    • Billing & Subscription Management
  • Getting Started

    • Getting Started with Xitoring
    • Workflows & Guides
    • Monitor Your First Server
    • Import / Migration
    • Migrate from UptimeRobot to Xitoring
    • Migrate from Pingdom to Xitoring
    • Migrate from Uptime.com to Xitoring
    • Migrate from BetterStack to Xitoring
  • Help & Support

    • FAQ & Troubleshooting
    • Glossary
  • Server Monitoring

    • Server Monitoring
    • Graphs
    • Live Statistics
    • Monitor Services
    • Auto-Triggers
  • Xitogent on Linux

    • Install Xitogent on Linux
    • Update Xitogent on Linux
    • Uninstall Xitogent on Linux
  • Xitogent on Windows

    • Install Xitogent on Windows
    • Uninstall Xitogent on Windows
    • Xitogent Service
    • Update Xitogent on Windows
    • Disk Performance (I/O)
  • Xitogent on Azure

    • Xitogent on Azure
    • Monitor Azure Linux VM
    • Monitor Azure Windows VM
  • Xitogent CLI

    • Xitogent CLI
    • Xitogent Pause/Unpause
    • Xitogent Status
    • Xitogent debug
    • Xitogent Diagnosis
    • Which data we collect
  • Xitoring CLI

    • Xitoring CLI
  • Uptime Monitoring

    • What is Uptime Monitoring
    • Monitoring Nodes (Geographic Locations)
    • What is Check
    • Auto-Discovery
    • Auto Fault Tolerance
    • Heartbeat Check
    • Ping Check
    • HTTP(S) Check
    • DNS Check
    • FTP Check
    • SMTP Check
    • IMAP Check
    • POP3 Check
    • TCP Check
    • UDP Check
  • SSL Monitoring

    • SSL Monitoring
  • Incidents

    • Incidents
    • Incident's Root Cause
    • Incidents Notification
    • Incident Notes
    • Resolving Incidents Manually
    • Incident Policy
  • Maintenance Schedule

    • Maintenance Schedule
  • Email Reports

    • Email Reports
  • Integrations

    • Integrations
    • Apache Integration
    • CoreDNS Integration
    • CouchDB Integration
    • Disk Health Integration
    • Docker Integration
    • Dovecot Integration
    • Exim Integration
    • HAProxy Integration
    • IIS Integration
    • InfluxDB Integration
    • Kafka Integration
    • KeyDB Integration
    • LiteSpeed Integration
    • MongoDB Integration
    • MySQL Integration
    • Netstat Integration
    • Nginx Integration
    • OpenLiteSpeed Integration
    • OpenVPN Integration
    • PHP-FPM Integration
    • Postfix Integration
    • PostgreSQL Integration
    • RabbitMQ integration
    • Redis Integration
    • MS SQL Server Integration
    • Supervisor Integration
    • Varnish Integration
    • Wireguard Integration
  • Notifications

    • Notifications
    • Creating Notification Roles
    • Email Integration
    • Mobile Push Notifications
    • SMS Integration
    • Phone call Integration
    • Webhook Integration
    • Integration for Slack
    • Telegram Integration
    • WhatsApp Integration
    • Mattermost Integration
    • Discord Integration
    • Google Chat Integration
    • Microsoft Teams Integration
    • Atlassian Opsgenie Integration
    • Splunk On-Call Integration
    • Pushover Integration
    • Pushbullet Integration
    • Gotify Integration
    • Ntfy Integration
    • Spike.sh Integration
    • PagerDuty Integration
    • Zapier Integration
    • AlertOps Integration
  • Status Page

    • Status page
  • 3rd Party Status Pages

    • Using 3rd party Status Pages
    • Atlassian Status Page Integration with Xitoring
    • Status.io Integration with Xitoring
    • Statuspal Integration with Xitoring
    • Instatus Integration with Xitoring
  • Dashboards

    • Main Dashboard
    • Custom Dashboards
  • Metrics

    • Metrics
  • MCP Server

    • Setup & Tool Reference

Webhook Integration

Webhooks are a simple and powerful way to send real-time notifications from Xitoring to your application. With webhook integration, you can receive alerts and incidents as they happen, enabling you to take immediate action and minimize downtime.

To set up webhook integration in Xitoring, follow these steps:

Create a Webhook URL

The first step is to create a webhook URL in your server or application. This is the URL where Xitoring will send the webhook notifications. Make sure the URL is publicly accessible and can receive HTTP POST requests.

Configure Webhook in Xitoring

Once you have a webhook URL, log in to your Xitoring account and go to the Notification Roles page. Click on the Notification role you want to add Webhook to it (or create a new notification role), and from the bottom of the page enter your Webhook URL in the field and then click on Send a Test Notification to get a test incident and make sure you have set up everything right.

Example request from Xitoring

The following is a full example of what Xitoring will POST to your Webhook URL:

As curl

curl -X 'POST' 'https://yourwebhook.app/cb92459602ccc67a8f7b' -H 'connection: close' -H 'content-type: application/x-www-form-urlencoded' -H 'content-length: 163' -H 'accept: */*' -H 'host: yourwebhook.app' -d $'id=0&group=test+group&sub_group=test+subgroup&server_id=0&check_id=0&label=server+label&name=&type=20&type_human_readable=ping&unit=&value=&status=0&incident_time='

Raw

id=0&group=test+group&sub_group=test+subgroup&server_id=0&check_id=0&label=server+label&name=&type=20&type_human_readable=ping&unit=&value=&status=0&incident_time=

Request breakdown

The following table is a guide to make it easy to integrate Xitoring webhook feature to your application.

VariableTypeExampleExplanation
idinteger0The incident ID
groupstring"test group"Name of the Group that check or server is assigned to
sub_groupstring"test sub-group"Name of the Sub-group that check or server is assigned to
server_idinteger1ID of the server
check_idinteger1ID of the Check
labelstring"test server"Server or Check label
namestring"total"Trigger name. e.g. total, used, keys
typeinteger20According to the type list below this table
type_human_readablestring"ping"ping, http, dns, ftp, ...
unitstring"mb"some incident have units like MB or GB, mostly metric values
valuesting""mostly metric incidents has values e.g. memory usage in time of incident
statusinteger00 is down and 1 is up
messagestring""The body of the message client gets
incident_timeinteger""time of the incident
Type mapping and definition
TypeID
Ping20
HTTP(s)21
DNS22
FTP23
SMTP24
POP325
IMAP26
SSL27
TCP28
UDP29
Heartbeat30
Load average1
CPU usage2
Memory usage3
Disk usage4
Disk I/O5
Network6
Bandwidth7
Nginx111
Apache112
FPM113
Redis114
KeyDB115
Supervisor116
Docker117
MySQL118
MongoDB119
HAProxy120
Services121
PostgreSQL122
IIS123
Varnish124
Disk Health125
RabbitMQ126
CouchDB127
OpenLiteSpeed128
Kafka129
LiteSpeed130
Last Updated: 4/10/25, 4:58 PM
Prev
Phone call Integration
Next
Integration for Slack