Rhombus Systems Access Control Integrations Webservice API
The Access Control Integrations Webservice API from Rhombus Systems — 101 operation(s) for access control integrations webservice.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/rhombus-systems-access-control-integrations-webservice-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
OpenAPI Specification
openapi: 3.2.0
info:
contact:
email: developer@rhombussystems.com
description: 'This API is for use by Rhombus customers and partners.
## Authentication
All requests require two headers:
- `x-auth-scheme` — The authentication scheme identifier. Use `api-token` for standard API key auth, or `partner-api-token` for partner API auth.
- `x-auth-apikey` — Your Rhombus API key.
Example:
```
POST /api/camera/getMinimalCameraStateList
x-auth-scheme: api-token
x-auth-apikey: YOUR_API_KEY
Content-Type: application/json
```'
title: Rhombus Access Control Integrations Webservice API
version: '1.0'
servers:
- description: Production Server
url: https://api2.rhombussystems.com
security:
- ApiKeyAuth: []
tags:
- name: Access Control Integrations Webservice
paths:
/api/integrations/accessControl/connectHoneywellElements:
post:
description: 'Step 1 of the Elements setup wizard: validate the API key against Honeywell Elements and persist on success. After this call, subsequent endpoints (sites, devices, update) resolve credentials from the stored row and never require the API key again.'
operationId: connectHoneywellElements
parameters:
- description: Authentication scheme identifier. Use `api-token` for standard API key authentication, `partner-api-token` for partner API key authentication. Must be paired with the `x-auth-apikey` header containing your API key.
example: api-token
in: header
name: x-auth-scheme
required: true
schema:
type: string
default: api-token
enum:
- api-token
- api
- partner-api-token
- partner-api
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/Integration_ConnectHoneywellElementsWSRequest'
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/BaseApiResponse'
description: OK
summary: Connect Honeywell Elements (validate + persist)
tags:
- Access Control Integrations Webservice
/api/integrations/accessControl/connectHoneywellNetBox:
post:
description: 'Activate the Honeywell NetBox integration for the calling org. NetBox is webhook-driven: the on-prem NetBox controller POSTs access events to a Rhombus webhook URL. On first activation the server generates the webhook rhombusToken and returns it (plus the fully-formed webhook URL); subsequent calls preserve the token so the configured forwarder keeps working as the door mapping changes. The request owns the door mapping and optional base URL.'
operationId: connectHoneywellNetBox
parameters:
- description: Authentication scheme identifier. Use `api-token` for standard API key authentication, `partner-api-token` for partner API key authentication. Must be paired with the `x-auth-apikey` header containing your API key.
example: api-token
in: header
name: x-auth-scheme
required: true
schema:
type: string
default: api-token
enum:
- api-token
- api
- partner-api-token
- partner-api
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/Integration_ConnectHoneywellNetBoxWSRequest'
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/Integration_ConnectHoneywellNetBoxIntegrationWSResponse'
description: OK
summary: Connect Honeywell NetBox (activate)
tags:
- Access Control Integrations Webservice
/api/integrations/accessControl/createOrUpdateHoneywellNetBoxIntegration:
post:
description: Activate or update the Honeywell NetBox integration from the on-prem side — the NetBox counterpart of createOrUpdateHoneywellOnGuardIntegration. Called by the Rhombus NetBox connector, which discovers portals via the NetBox GetPortals API and owns the door inventory; the console owns camera/location assignments. First activation (blank rhombusToken, no existing integration) generates the webhook token; re-calls merge the door map by portal key without overwriting console-made assignments, and keys absent from the request are preserved.
operationId: createOrUpdateHoneywellNetBoxIntegration
parameters:
- description: Authentication scheme identifier. Use `api-token` for standard API key authentication, `partner-api-token` for partner API key authentication. Must be paired with the `x-auth-apikey` header containing your API key.
example: api-token
in: header
name: x-auth-scheme
required: true
schema:
type: string
default: api-token
enum:
- api-token
- api
- partner-api-token
- partner-api
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/Integration_CreateOrUpdateHoneywellNetBoxIntegrationWSRequest'
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/Integration_CreateOrUpdateHoneywellNetBoxIntegrationWSResponse'
description: OK
summary: Create or update Honeywell NetBox integration (on-prem connector)
tags:
- Access Control Integrations Webservice
/api/integrations/accessControl/createOrUpdateHoneywellOnGuardIntegration:
post:
description: Idempotent activation/update endpoint called by the OnGuard side from its setup tool. Generates the webhook token and pre-shared HMAC secret on first call; preserves both on subsequent calls so the deployed DLL keeps working as the door mapping changes. The request owns the door mapping; behavior flags (face recognition, clip saving, etc.) are managed separately from the Rhombus console.
operationId: createOrUpdateHoneywellOnGuardIntegration
parameters:
- description: Authentication scheme identifier. Use `api-token` for standard API key authentication, `partner-api-token` for partner API key authentication. Must be paired with the `x-auth-apikey` header containing your API key.
example: api-token
in: header
name: x-auth-scheme
required: true
schema:
type: string
default: api-token
enum:
- api-token
- api
- partner-api-token
- partner-api
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/Integration_CreateOrUpdateHoneywellOnGuardIntegrationWSRequest'
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/Integration_CreateOrUpdateHoneywellOnGuardIntegrationWSResponse'
description: OK
summary: Create or update the Honeywell OnGuard integration
tags:
- Access Control Integrations Webservice
/api/integrations/accessControl/deleteAmtIntegration:
post:
description: Delete Amt badge integration
operationId: deleteAmtIntegration
parameters:
- description: Authentication scheme identifier. Use `api-token` for standard API key authentication, `partner-api-token` for partner API key authentication. Must be paired with the `x-auth-apikey` header containing your API key.
example: api-token
in: header
name: x-auth-scheme
required: true
schema:
type: string
default: api-token
enum:
- api-token
- api
- partner-api-token
- partner-api
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/Integration_BaseIntegrationWSRequest'
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/BaseApiResponse'
description: OK
summary: Delete AMT badge integration
tags:
- Access Control Integrations Webservice
/api/integrations/accessControl/deleteAvigilonAltaIntegrationV2:
post:
description: Delete Avigilon Alta badge integration V2
operationId: deleteAvigilonAltaIntegrationV2
parameters:
- description: Authentication scheme identifier. Use `api-token` for standard API key authentication, `partner-api-token` for partner API key authentication. Must be paired with the `x-auth-apikey` header containing your API key.
example: api-token
in: header
name: x-auth-scheme
required: true
schema:
type: string
default: api-token
enum:
- api-token
- api
- partner-api-token
- partner-api
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/Integration_BaseIntegrationWSRequest'
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/BaseApiResponse'
description: OK
summary: Delete Avigilon Alta badge integration V2
tags:
- Access Control Integrations Webservice
/api/integrations/accessControl/deleteBoulevardIntegration:
post:
description: Delete Boulevard integration settings
operationId: deleteBoulevardIntegration
parameters:
- description: Authentication scheme identifier. Use `api-token` for standard API key authentication, `partner-api-token` for partner API key authentication. Must be paired with the `x-auth-apikey` header containing your API key.
example: api-token
in: header
name: x-auth-scheme
required: true
schema:
type: string
default: api-token
enum:
- api-token
- api
- partner-api-token
- partner-api
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/Integration_BaseIntegrationWSRequest'
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/BaseApiResponse'
description: OK
summary: Delete Boulevard integration
tags:
- Access Control Integrations Webservice
/api/integrations/accessControl/deleteBrivoIntegration:
post:
description: Delete Brivo badge integration
operationId: deleteBrivoIntegration
parameters:
- description: Authentication scheme identifier. Use `api-token` for standard API key authentication, `partner-api-token` for partner API key authentication. Must be paired with the `x-auth-apikey` header containing your API key.
example: api-token
in: header
name: x-auth-scheme
required: true
schema:
type: string
default: api-token
enum:
- api-token
- api
- partner-api-token
- partner-api
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/Integration_BaseIntegrationWSRequest'
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/Integration_UpdateOrgIntegrationsWSResponse'
description: OK
summary: Delete Brivo badge integration
tags:
- Access Control Integrations Webservice
/api/integrations/accessControl/deleteBrivoIntegrationV2:
post:
description: Delete Brivo badge integration V2
operationId: deleteBrivoIntegrationV2
parameters:
- description: Authentication scheme identifier. Use `api-token` for standard API key authentication, `partner-api-token` for partner API key authentication. Must be paired with the `x-auth-apikey` header containing your API key.
example: api-token
in: header
name: x-auth-scheme
required: true
schema:
type: string
default: api-token
enum:
- api-token
- api
- partner-api-token
- partner-api
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/Integration_BaseIntegrationWSRequest'
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/BaseApiResponse'
description: OK
summary: Delete Brivo badge integration V2
tags:
- Access Control Integrations Webservice
/api/integrations/accessControl/deleteButterflymxIntegration:
post:
description: Delete ButterflyMX badge integration
operationId: deleteButterflymxIntegration
parameters:
- description: Authentication scheme identifier. Use `api-token` for standard API key authentication, `partner-api-token` for partner API key authentication. Must be paired with the `x-auth-apikey` header containing your API key.
example: api-token
in: header
name: x-auth-scheme
required: true
schema:
type: string
default: api-token
enum:
- api-token
- api
- partner-api-token
- partner-api
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/Integration_BaseIntegrationWSRequest'
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/BaseApiResponse'
description: OK
summary: Delete ButterflyMX badge integration
tags:
- Access Control Integrations Webservice
/api/integrations/accessControl/deleteButterflymxIntegrationV2:
post:
description: Delete ButterflyMX badge integration V2
operationId: deleteButterflymxIntegrationV2
parameters:
- description: Authentication scheme identifier. Use `api-token` for standard API key authentication, `partner-api-token` for partner API key authentication. Must be paired with the `x-auth-apikey` header containing your API key.
example: api-token
in: header
name: x-auth-scheme
required: true
schema:
type: string
default: api-token
enum:
- api-token
- api
- partner-api-token
- partner-api
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/Integration_BaseIntegrationWSRequest'
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/BaseApiResponse'
description: OK
summary: Delete ButterflyMX badge integration V2
tags:
- Access Control Integrations Webservice
/api/integrations/accessControl/deleteGeneaIntegration:
post:
description: Delete Genea badge integration
operationId: deleteGeneaIntegration
parameters:
- description: Authentication scheme identifier. Use `api-token` for standard API key authentication, `partner-api-token` for partner API key authentication. Must be paired with the `x-auth-apikey` header containing your API key.
example: api-token
in: header
name: x-auth-scheme
required: true
schema:
type: string
default: api-token
enum:
- api-token
- api
- partner-api-token
- partner-api
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/Integration_BaseIntegrationWSRequest'
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/BaseApiResponse'
description: OK
summary: Delete Genea badge integration
tags:
- Access Control Integrations Webservice
/api/integrations/accessControl/deleteGeneaIntegrationV2:
post:
description: Delete Genea badge integration V2
operationId: deleteGeneaIntegrationV2
parameters:
- description: Authentication scheme identifier. Use `api-token` for standard API key authentication, `partner-api-token` for partner API key authentication. Must be paired with the `x-auth-apikey` header containing your API key.
example: api-token
in: header
name: x-auth-scheme
required: true
schema:
type: string
default: api-token
enum:
- api-token
- api
- partner-api-token
- partner-api
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/Integration_BaseIntegrationWSRequest'
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/BaseApiResponse'
description: OK
summary: Delete Genea badge integration V2
tags:
- Access Control Integrations Webservice
/api/integrations/accessControl/deleteHoneywellElementsIntegration:
post:
description: Delete Honeywell Elements integration
operationId: deleteHoneywellElementsIntegration
parameters:
- description: Authentication scheme identifier. Use `api-token` for standard API key authentication, `partner-api-token` for partner API key authentication. Must be paired with the `x-auth-apikey` header containing your API key.
example: api-token
in: header
name: x-auth-scheme
required: true
schema:
type: string
default: api-token
enum:
- api-token
- api
- partner-api-token
- partner-api
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/Integration_BaseIntegrationWSRequest'
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/BaseApiResponse'
description: OK
summary: Delete Honeywell Elements integration
tags:
- Access Control Integrations Webservice
/api/integrations/accessControl/deleteHoneywellNetBoxIntegration:
post:
description: Delete Honeywell NetBox integration
operationId: deleteHoneywellNetBoxIntegration
parameters:
- description: Authentication scheme identifier. Use `api-token` for standard API key authentication, `partner-api-token` for partner API key authentication. Must be paired with the `x-auth-apikey` header containing your API key.
example: api-token
in: header
name: x-auth-scheme
required: true
schema:
type: string
default: api-token
enum:
- api-token
- api
- partner-api-token
- partner-api
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/Integration_BaseIntegrationWSRequest'
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/BaseApiResponse'
description: OK
summary: Delete Honeywell NetBox integration
tags:
- Access Control Integrations Webservice
/api/integrations/accessControl/deleteHoneywellOnGuardIntegration:
post:
description: 'Delete Honeywell OnGuard integration. Callable from the Rhombus console (admin) or from the OnGuard side (uninstall). Idempotent per deployment: deleting a rhombusToken that is unknown or already deleted returns success, so the client may safely retry after a network failure.'
operationId: deleteHoneywellOnGuardIntegration
parameters:
- description: Authentication scheme identifier. Use `api-token` for standard API key authentication, `partner-api-token` for partner API key authentication. Must be paired with the `x-auth-apikey` header containing your API key.
example: api-token
in: header
name: x-auth-scheme
required: true
schema:
type: string
default: api-token
enum:
- api-token
- api
- partner-api-token
- partner-api
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/Integration_DeleteHoneywellOnGuardIntegrationWSRequest'
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/BaseApiResponse'
description: OK
summary: Delete Honeywell OnGuard integration
tags:
- Access Control Integrations Webservice
/api/integrations/accessControl/deleteInnerRangeIntegration:
post:
description: Delete Inner Range integration
operationId: deleteInnerRangeIntegration
parameters:
- description: Authentication scheme identifier. Use `api-token` for standard API key authentication, `partner-api-token` for partner API key authentication. Must be paired with the `x-auth-apikey` header containing your API key.
example: api-token
in: header
name: x-auth-scheme
required: true
schema:
type: string
default: api-token
enum:
- api-token
- api
- partner-api-token
- partner-api
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/Integration_BaseIntegrationWSRequest'
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/BaseApiResponse'
description: OK
summary: Delete Inner Range integration
tags:
- Access Control Integrations Webservice
/api/integrations/accessControl/deleteKisiIntegration:
post:
deprecated: true
description: Delete Kisi badge integration
operationId: deleteKisiIntegration
parameters:
- description: Authentication scheme identifier. Use `api-token` for standard API key authentication, `partner-api-token` for partner API key authentication. Must be paired with the `x-auth-apikey` header containing your API key.
example: api-token
in: header
name: x-auth-scheme
required: true
schema:
type: string
default: api-token
enum:
- api-token
- api
- partner-api-token
- partner-api
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/Integration_BaseIntegrationWSRequest'
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/BaseApiResponse'
description: OK
summary: Delete Kisi badge integration
tags:
- Access Control Integrations Webservice
/api/integrations/accessControl/deleteKisiIntegrationV2:
post:
description: Delete Kisi badge integration V2
operationId: deleteKisiIntegrationV2
parameters:
- description: Authentication scheme identifier. Use `api-token` for standard API key authentication, `partner-api-token` for partner API key authentication. Must be paired with the `x-auth-apikey` header containing your API key.
example: api-token
in: header
name: x-auth-scheme
required: true
schema:
type: string
default: api-token
enum:
- api-token
- api
- partner-api-token
- partner-api
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/Integration_BaseIntegrationWSRequest'
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/BaseApiResponse'
description: OK
summary: Delete Kisi badge integration V2
tags:
- Access Control Integrations Webservice
/api/integrations/accessControl/deleteOpenpathIntegration:
post:
description: Delete Openpath badge integration
operationId: deleteOpenpathIntegration
parameters:
- description: Authentication scheme identifier. Use `api-token` for standard API key authentication, `partner-api-token` for partner API key authentication. Must be paired with the `x-auth-apikey` header containing your API key.
example: api-token
in: header
name: x-auth-scheme
required: true
schema:
type: string
default: api-token
enum:
- api-token
- api
- partner-api-token
- partner-api
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/Integration_BaseIntegrationWSRequest'
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/BaseApiResponse'
description: OK
summary: Delete Openpath badge integration
tags:
- Access Control Integrations Webservice
/api/integrations/accessControl/deleteOpentechAllianceIntegration:
post:
description: Delete Opentech Alliance integration
operationId: deleteOpentechAllianceIntegration
parameters:
- description: Authentication scheme identifier. Use `api-token` for standard API key authentication, `partner-api-token` for partner API key authentication. Must be paired with the `x-auth-apikey` header containing your API key.
example: api-token
in: header
name: x-auth-scheme
required: true
schema:
type: string
default: api-token
enum:
- api-token
- api
- partner-api-token
- partner-api
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/Integration_BaseIntegrationWSRequest'
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/BaseApiResponse'
description: OK
summary: Delete Opentech Alliance integration
tags:
- Access Control Integrations Webservice
/api/integrations/accessControl/deleteOpentechAllianceIntegrationV2:
post:
description: Delete Opentech Alliance integration
operationId: deleteOpentechAllianceIntegrationV2
parameters:
- description: Authentication scheme identifier. Use `api-token` for standard API key authentication, `partner-api-token` for partner API key authentication. Must be paired with the `x-auth-apikey` header containing your API key.
example: api-token
in: header
name: x-auth-scheme
required: true
schema:
type: string
default: api-token
enum:
- api-token
- api
- partner-api-token
- partner-api
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/Integration_BaseIntegrationWSRequest'
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/BaseApiResponse'
description: OK
summary: Delete Opentech Alliance integration V2
tags:
- Access Control Integrations Webservice
/api/integrations/accessControl/deletePdkIntegration:
post:
description: Delete ProDataKey badge integration
operationId: deletePdkIntegration
parameters:
- description: Authentication scheme identifier. Use `api-token` for standard API key authentication, `partner-api-token` for partner API key authentication. Must be paired with the `x-auth-apikey` header containing your API key.
example: api-token
in: header
name: x-auth-scheme
required: true
schema:
type: string
default: api-token
enum:
- api-token
- api
- partner-api-token
- partner-api
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/Integration_BaseIntegrationWSRequest'
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/BaseApiResponse'
description: OK
summary: Delete ProDataKey badge integration
tags:
- Access Control Integrations Webservice
/api/integrations/accessControl/deletePdkIntegrationV2:
post:
description: Delete ProDataKey badge integration
operationId: deletePdkIntegrationV2
parameters:
- description: Authentication scheme identifier. Use `api-token` for standard API key authentication, `partner-api-token` for partner API key authentication. Must be paired with the `x-auth-apikey` header containing your API key.
example: api-token
in: header
name: x-auth-scheme
required: true
schema:
type: string
default: api-token
enum:
- api-token
- api
- partner-api-token
- partner-api
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/Integration_BaseIntegrationWSRequest'
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/BaseApiResponse'
description: OK
summary: Delete ProDataKey badge integration V2
tags:
- Access Control Integrations Webservice
/api/integrations/accessControl/deletePlaceOsIntegration:
post:
description: Delete PlaceOs badge integration
operationId: deletePlaceOsIntegration
parameters:
- description: Authentication scheme identifier. Use `api-token` for standard API key authentication, `partner-api-token` for partner API key authentication. Must be paired with the `x-auth-apikey` header containing your API key.
example: api-token
in: header
name: x-auth-scheme
required: true
schema:
type: string
default: api-token
enum:
- api-token
- api
- partner-api-token
- partner-api
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/Integration_BaseIntegrationWSRequest'
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/BaseApiResponse'
description: OK
summary: Delete PlaceOs badge integration
tags:
- Access Control Integrations Webservice
/api/integrations/accessControl/deletePlaceOsIntegrationV2:
post:
description: Delete PlaceOs badge integration
operationId: deletePlaceOsIntegrationV2
parameters:
- description: Authentication scheme identifier. Use `api-token` for standard API key authentication, `partner-api-token` for partner API key authentication. Must be paired with the `x-auth-apikey` header containing your API key.
example: api-token
in: header
name: x-auth-scheme
required: true
schema:
type: string
default: api-token
enum:
- api-token
- api
- partner-api-token
- partner-api
requestBody:
content:
applicatio
# --- truncated at 32 KB (282 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/rhombus-systems/refs/heads/main/openapi/rhombus-systems-access-control-integrations-webservice-api-openapi.yml