Rhombus Webhooks

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

Subscribe to Events

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

Events Occur

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

Receive Notifications

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

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:

{
  "uuid": "event-uuid-here",
  "orgUuid": "org-uuid-here",
  "ruleUuid": "rule-uuid-here",
  "triggeredTimestampMs": 1712678400000,
  "deviceEvents": [
    {
      "eventUuid": "device-event-uuid-here",
      "deviceUuid": "camera-uuid-here",
      "deviceType": "CAMERA",
      "locationUuid": "location-uuid-here",
      "timestampMs": 1712678400000,
      "activities": ["MOTION_HUMAN"]
    }
  ],
  "ruleTriggers": [
    {
      "type": "DEVICE_ACTIVITY_EVENT"
    }
  ]
}

Webhooks are triggered by the rules you configure in Rhombus. Each payload identifies the rule that fired (ruleUuid), the triggers that matched (ruleTriggers), and the underlying device events (deviceEvents). The specific fields present depend on the triggering event type, so set up a test webhook endpoint to inspect the full payload for your rules.

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

Getting Started

Implementation Guides

Real-time Events

How Webhooks Work

Event Types

Camera Events

Access Control Events

Sensor Events

Device Events

Sample Webhook Payload

Managing Webhooks via the API

Implementation Guide

No-Code Alternatives

​How Webhooks Work

​Event Types

Camera Events

Access Control Events

Sensor Events

Device Events

​Sample Webhook Payload

​Managing Webhooks via the API

​Implementation Guide

​No-Code Alternatives

How Webhooks Work

Event Types

Sample Webhook Payload

Managing Webhooks via the API

Implementation Guide

No-Code Alternatives