Reference · built on requestConnectorAccess control & video

Rhombus

Cameras, doors, credentials, climate sensors, and policy alerts from Rhombus, with door release, credential, lockdown, and clip actions.

Request accessPricing ↗

About

Rhombus sells cloud-managed cameras, access control doors and credentials, and environmental sensors, administered in the Rhombus Console. One REST API at api2.rhombussystems.com, or api2.eu.rhombussystems.com for EU organizations, covers cameras, video, access control, climate, schedules, policies, and webhooks. Webhook subscriptions push policy alerts from cameras, doors, sensors, and devices to your endpoint.

Through Fibric, an operator reads door state and sensor readings, fetches the frame for the moment, and proposes a door release, a credential change, a lockdown, or a saved clip. You decide; the call is then made a single time and logged with its undo.

This is a reference listing. It documents what Fibric would read from Rhombus and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Cameras and their mediaRegion through POST /api/camera/getMinimalCameraStateList, snapshots, and exact frames through POST /api/video/getExactFrameUri
  • Access-controlled doors through /api/component/findAccessControlledDoors, with defaultState, remoteUnlockEnabled, and unlockTimeSec
  • Credentials by user through /api/accesscontrol/findAccessControlCredentialByUser, and lockdown plans through findLockdownPlans
  • Climate sensors and readings through /api/climate/getMinimalClimateStateList and getClimateEventsForSensor: temperature, humidity, IAQ, CO2, TVOC, PM2.5
  • Environmental gateway states and events, and climate alert policies
  • Webhook deliveries with deviceEvents and ruleTriggers for motion, analytics, door open and forced entry, credential scans, and threshold alerts

Proposed actions

  • Target capability: propose a remote door release through POST /api/accesscontrol/unlockAccessControlledDoor
  • Target capability: propose suspending, unsuspending, or revoking a credential, or assigning one to a user
  • Target capability: propose adding users to an access group, or creating an access grant with doors, groups, and a weekly schedule
  • Target capability: propose activating or deactivating a lockdown plan for a location
  • Target capability: propose a saved clip through POST /api/video/spliceV3, or a time-limited shared live stream

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Respond to a forced or propped door

    A door forced entry or held open alert arrives by webhook. The operator pulls the exact frame from the nearest camera and proposes the alert to your team with the image attached.

    With Door Held Open, Access Anomaly

  • Revoke credentials when someone leaves

    From a leaver record, the operator proposes revoking each credential returned by findAccessControlCredentialByUser and removing the user from access groups. You approve; the receipt lists each change.

    With Access Offboarding

  • Watch cold rooms and server rooms

    Climate readings are compared with the thresholds in your climate policies. A sustained excursion becomes a proposed work order with the reading history attached.

    With Cold Room Watch, Indoor Air

  • Keep cameras and sensors online

    Device offline events from webhooks are held for your grace period, then proposed as tickets with the device, location, and last reading.

    With Camera Health, Sensor Health

Requirements

  • A Rhombus organization and an API key generated in the Rhombus Console
  • The base URL for your region: api2.rhombussystems.com, or the .eu. variant for EU organizations
  • An HTTPS endpoint to receive webhook deliveries, registered as a webhook subscription with event filters
  • Remote release enabled on each door the operator may open, as shown by remoteUnlockEnabled
Authentication
An API key generated in the Rhombus Console, sent on every request as x-auth-apikey with x-auth-scheme set to api-token.

Limits

  • Rate limits are enforced per organization: every API key shares one token bucket, with burst capacity about ten times the refill rate
  • A 429 carries Retry-After of at least one second; Rhombus publishes no fixed requests-per-second figure and raises limits through support
  • Shared HLS URLs are time-limited credentials; set expirationTimeSecs and do not expose them without an expiry policy
  • The webhook guide describes payloads but no signature scheme; verify deliveries by another means

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Rhombus ↗

Questions and answers

How are Rhombus rate limits enforced?
Per organization. Every API key and OAuth token in your organization shares one token bucket: a sustained refill rate in requests per second, plus burst capacity roughly ten times that rate. Exceeding it returns 429 with a Retry-After header of at least one second. Higher limits come from Rhombus support.
Can an API call open a door remotely?
Yes. POST /api/accesscontrol/unlockAccessControlledDoor with accessControlledDoorUuid returns SUCCESS or ERROR. The door listing shows whether remoteUnlockEnabled is on and the unlockTimeSec that applies. Lockdown plans are activated per location through activateLockdownForLocation.
Which webhook events can be sent?
Rhombus lists camera events such as motion, analytics alerts, saved clips, and AI detections; access control events such as door open and close, forced entry, access granted and denied, and credential scans; sensor threshold alerts for temperature, humidity, and air quality; and device button presses and online or offline changes.
Ask about Rhombus

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Rhombus through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy