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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Rhombus Systems

Rhombus Systems Alarm Monitoring Keypad Webservice API

The Alarm Monitoring Keypad Webservice API from Rhombus Systems — 5 operation(s) for alarm monitoring keypad webservice.

Documentation Provider Profile APIs.io OpenAPI GitHub

Rhombus Systems Alarm Monitoring Keypad 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 Alarm Monitoring Keypad 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 14 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 14 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
Contact
developer@rhombussystems.com
Resource Areas
1

Authentication & Security 1

Rhombus Systems Alarm Monitoring Keypad 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.

Alarm Monitoring Keypad Webservice 5
POST
/api/keypad/claimKeypadActivationToken
Claim keypad activation token
claimKeypadActivationToken 1 param body → 200
POST
/api/keypad/getKeypadsForLocation
Get keypads for location
getKeypadsForLocation 1 param body → 200
POST
/api/keypad/getKeypadsForOrg
Get keypads for organization
getKeypadsForOrg 1 param body → 200
POST
/api/keypad/unregisterKeypad
Unregister keypad
unregisterKeypad 1 param body → 200
POST
/api/keypad/updateKeypad
Update keypad
updateKeypad 1 param body → 200

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are KeypadConfigType (24 properties), Keypad_UpdateKeypadRequest (18 properties), QualifiedAddressType (6 properties), Keypad_GetKeypadsForOrgWSResponse (4 properties). Each schema is shown below with its type and property counts.

Keypad_UnregisterKeypadRequest
object
Request object for unregistering a keypad.
1 property
QualifiedAddressType
object
Qualified address information for the keypad location
6 properties
Keypad_ClaimKeypadActivationTokenResponse
object
Response object for claiming a keypad activation token.
3 properties
KeypadPlatformEnum
string
The keypad platform (IOS or ANDROID)
Keypad_GetKeypadsForOrgWSResponse
object
Response object containing all registered keypads for an organization.
4 properties
Keypad_GetKeypadsForLocationWSRequest
object
Request object for getting all registered keypads for a specific location.
1 property
Keypad_ClaimKeypadActivationTokenRequest
object
Request object for claiming a keypad activation token to connect a keypad to Rhombus services.
4 properties
Keypad_UpdateKeypadResponse
object
Response object for updating keypad settings.
3 properties
Keypad_UnregisterKeypadResponse
object
Response object for unregistering a keypad.
3 properties
KeypadConfigType
object
List of all registered keypads for the organization
24 properties
KeypadConnectionStateEnum
string
Keypad_UpdateKeypadRequest
object
Request object for updating keypad settings and configuration.
18 properties
Keypad_GetKeypadsForLocationWSResponse
object
Response object containing all registered keypads for a specific location.
4 properties
Keypad_GetKeypadsForOrgWSRequest
object
Request object for getting all registered keypads for an organization.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

rhombus-systems-alarm-monitoring-keypad-webservice-api-openapi.yml Raw ↑

Other APIs Rhombus Systems publishes across the network.

Rhombus Console WebSocket API
AE Profile APIs.io
Rhombus Systems Access Control Integrations Webservice API
AE Profile APIs.io
Rhombus Systems Access Control Webservice API
AE Profile APIs.io
Rhombus Systems Alert Monitoring Webservice API
AE Profile APIs.io
Rhombus Systems AudioGateway Webservice API
AE Profile APIs.io
Rhombus Systems AudioPlayback Webservice API
AE Profile APIs.io
Rhombus Systems Badge Reader Webservice API
AE Profile APIs.io
Rhombus Systems BLE Webservice API
AE Profile APIs.io
Rhombus Systems Button Webservice API
AE Profile APIs.io
Rhombus Systems Camera Webservice API
AE Profile APIs.io
Rhombus Systems ClaimKey Webservice API
AE Profile APIs.io
Rhombus Systems Climate Webservice API
AE Profile APIs.io
#Alarm Monitoring Keypad Webservice
← Back to R APIs
API Details
ID
rhombus-systems:rhombus-systems-alarm-monitoring-keypad-webservice-api
Base URL
https://api2.rhombussystems.com/api
Docs
https://api-docs.rhombus.community/
Provider
Rhombus Systems
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=rhombus-systems-alarm-monitoring-keypad-webservice-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/rhombus-systems-alarm-monitoring-keypad-webservice-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Rhombus Systems Alarm Monitoring Keypad 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.