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 Feature Webservice API

The Feature Webservice API from Rhombus Systems — 5 operation(s) for feature webservice.

Rhombus Systems Feature 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 Feature Webservice. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 5 operations across 5 paths, and defines 16 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.

5 operations 5 paths 16 schemas 5 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 Feature 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 5

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

Feature Webservice 5
POST
/api/feature/getDeviceEventTypes
Get possible event types for specified device
getDeviceEventTypes 1 param body → 200
POST
/api/feature/getDeviceFeatures
Get enabled features for a device
getDeviceFeatures 1 param body → 200
POST
/api/feature/getDeviceFeaturesList
Get enabled features for all devices in an org
getDeviceFeaturesList 1 param body → 200
POST
/api/feature/getFeatureCompatabilityMatrix
Get feature compatibility matrix
getFeatureCompatabilityMatrix 1 param body → 200
POST
/api/feature/updateDeviceFeatures
Update enabled features for a device
updateDeviceFeatures 1 param body → 200

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are FeatureCompatabilityType (8 properties), Feature_GetFeatureCompatabilityMatrixWSResponse (4 properties), Feature_GetDeviceFeaturesWSResponse (4 properties), Feature_GetDeviceFeaturesListWSResponse (4 properties). Each schema is shown below with its type and property counts.

Feature_UpdateDeviceFeaturesWSResponse
object
Response object for updating enabled features for a device.
3 properties
ActivityEnum
string
LicenseEnum
string
DeviceFeatureEnum
string
Feature_GetDeviceFeaturesWSResponse
object
Response object containing enabled features for a device.
4 properties
Feature_GetFeatureCompatabilityMatrixWSResponse
object
Response object containing the feature compatibility matrix.
4 properties
Feature_GetDeviceEventTypesWSRequest
object
Request object for retrieving possible event types for a device based on enabled features.
1 property
Feature_GetDeviceFeaturesWSRequest
object
Request object for retrieving enabled features for a device.
1 property
Feature_GetFeatureCompatabilityMatrixWSRequest
object
Request object for retrieving the feature compatibility matrix.
Feature_GetDeviceFeaturesListWSRequest
object
Request object for retrieving enabled features for multiple devices in an organization.
1 property
Feature_UpdateDeviceFeaturesWSRequest
object
Request object for updating enabled features for a device.
2 properties
FeatureCompatabilityType
object
List of feature compatibility information
8 properties
Feature_DeviceFeaturesType
object
Device features configuration with feature enablement mapping.
2 properties
Feature_GetDeviceFeaturesListWSResponse
object
Response object containing enabled features for multiple devices in an organization.
4 properties
HardwareVariationEnum
string
Feature_GetDeviceEventTypesWSResponse
object
Response object containing possible event types for a device based on enabled features.
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

rhombus-systems-feature-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 Feature 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.