How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Rhombus Systems Rules Records Webservice API

The Rules Records Webservice API from Rhombus Systems — 3 operation(s) for rules records webservice.

Rhombus Systems Rules Records Webservice API is one of 65 APIs that Rhombus Systems publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Rules Records Webservice. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 3 operations across 3 paths, and defines 32 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api2.rhombussystems.com.

3 operations 3 paths 32 schemas 3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api2.rhombussystems.com/api
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Rhombus Systems Rules Records Webservice API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-auth-apikey (ApiKeyAuth). By default, every request must be authenticated.

  • ApiKeyAuth — Your Rhombus API key. Must be accompanied by the x-auth-scheme header set to api-token (or partner-api-token for partner endpoints).

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 3 POST. Each is listed below with its method, path, parameters, and response codes.

Rules Records Webservice 3
POST
/api/rulesRecords/deleteRulesEventRecord
Delete rules event record
deleteRulesEventRecord 1 param body → 200
POST
/api/rulesRecords/getLatestRulesEventRecords
Get latest rules event records
getLatestRulesEventRecords 1 param body → 200
POST
/api/rulesRecords/getRulesEventRecords
Get rules event records
getRulesEventRecords 1 param body → 200

Schemas 32

The contract defines 32 schemas that model the data the API accepts and returns. The most detailed are RulesEventRecordType (20 properties), DeviceEventRecordType (10 properties), TriggerComponentRelayActionRecordType (7 properties), ChangeComponentCompositeAccessStateRecordType (6 properties). Each schema is shown below with its type and property counts.

AlertActionRecordType
object
2 properties
CancelLoopingAudioPlaybackActionRecordType
object
1 property
Rules_records_DeleteRulesEventRecordWSRequest
object
Request object for deleting a rules event record.
1 property
RulesEventRecordType
object
List of rules event records
20 properties
CreateAlarmActionRecordType
object
5 properties
LiveNotificationActionRecordType
object
1 property
AlertMonitoringEventRecordType
object
5 properties
Rules_records_GetRulesEventRecordsWSResponse
object
Response object for getting rules event records.
1 property
Rules_records_GetRulesEventRecordsWSRequest
object
Request object for getting rules event records.
3 properties
TriggerComponentRelayActionRecordType
object
7 properties
ChangeComponentCompositeAccessStateRecordType
object
6 properties
AudioPlaybackActionRecordType
object
2 properties
AlertActionStatusEnum
string
IntegrationActionStatusEnum
string
EnableDisableAudioRecordActionRecordType
object
3 properties
ActivateLocationLockdownActionRecordType
object
3 properties
Rules_records_GetLatestRulesEventRecordsWSResponse
object
Response object for getting latest rules event records.
1 property
AudioGatewayStatusEnum
string
LiveNotificationActionStatusEnum
string
DeviceEventRecordType
object
10 properties
AccessControlledDoorStateEnumType
string
DeviceTypeEnum
string
Rules_records_DeleteRulesEventRecordWSResponse
object
Response object for deleting a rules event record.
ComponentRelayOutputTypeEnum
string
Rules_records_GetLatestRulesEventRecordsWSRequest
object
Request object for getting latest rules event records.
3 properties
HardwareVariationEnum
string
ActivityEnum
string
AlertMonitoringRulesEventTypeEnum
string
ScheduledEventRecordType
object
1 property
VisionLLMEventRecordType
object
5 properties
GenericRelayStateEnumType
string
UnlockDoorActionRecordType
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

rhombus-systems-rules-records-webservice-api-openapi.yml Raw ↑

Other APIs Rhombus Systems publishes across the network.

Rhombus Console WebSocket API
Rhombus Systems Access Control Integrations Webservice API
Rhombus Systems Access Control Webservice API
Rhombus Systems Alarm Monitoring Keypad Webservice API
Rhombus Systems Alert Monitoring Webservice API
Rhombus Systems AudioGateway Webservice API
Rhombus Systems AudioPlayback Webservice API
Rhombus Systems Badge Reader Webservice API
Rhombus Systems BLE Webservice API
Rhombus Systems Button Webservice API
Rhombus Systems Camera Webservice API
Rhombus Systems ClaimKey Webservice API
Where this information came from

This is an independent, third-party profile of Rhombus Systems Rules Records Webservice API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.