Skip to main content

Documentation Index

Fetch the complete documentation index at: https://api-docs.rhombus.community/llms.txt

Use this file to discover all available pages before exploring further.

Rhombus webhooks deliver real-time HTTP POST notifications to your server when events occur — door opens, camera alerts, sensor threshold breaches, button presses, and more. Instead of polling the API, your application receives events as they happen.

​
How Webhooks Work

1

Subscribe to Events

Use the Rhombus API to register a webhook URL and specify which event types you want to receive.
2

Events Occur

When a subscribed event happens in your Rhombus environment (e.g., a door is forced open), the system generates an event payload.
3

Receive Notifications

Rhombus sends an HTTP POST request to your registered URL with the event details as a JSON payload.
4

Process & Respond

Your server processes the event and returns a 200 OK response to acknowledge receipt.

​
Event Types

Rhombus supports webhook notifications for a wide range of events across your security infrastructure:

Camera Events

Motion detection, analytics alerts, video clips saved, AI-powered detections

Access Control Events

Door open/close, forced entry, access granted/denied, credential scans

Sensor Events

Temperature, humidity, and air quality threshold alerts

Device Events

Button presses, device online/offline status changes

​
Sample Webhook Payload

When an event triggers a webhook, Rhombus sends a POST request to your URL with a JSON payload: 
{
  "eventType": "POLICY_ALERT",
  "timestamp": 1712678400000,
  "orgUuid": "org-uuid-here",
  "data": {
    "deviceUuid": "camera-uuid-here",
    "deviceName": "Lobby Camera",
    "policyName": "Motion Detection",
    "alertUuid": "alert-uuid-here"
  }
}
The exact payload structure varies by event type. Set up a test webhook endpoint to inspect the full payload for your specific events.

​
Managing Webhooks via the API

Use the Webhook Integrations endpoints to manage your webhook subscriptions:
  • Create a webhook subscription with your endpoint URL and event filters
  • List active webhook subscriptions for your organization
  • Update existing subscriptions to change URLs or event types
  • Delete subscriptions you no longer need
Browse webhook endpoints in the API Reference under the Webhook Integrations section.

​
Implementation Guide

For a complete guide on setting up a webhook listener — including receiving webhooks on servers behind firewalls using reverse SSH tunneling — see the Webhook Listener Implementation.

​
No-Code Alternatives

If you prefer a visual workflow builder over writing custom webhook handlers, Rhombus integrates with:
  • Zapier — instant triggers for rule events, button presses, door events, and sensor alerts
  • Make.com — webhook triggers with advanced data routing
  • n8n — self-hosted webhook processing with AI agent capabilities
Last modified on April 29, 2026