Rhombus Systems

Rhombus Systems Access Control Integrations Webservice API

The Access Control Integrations Webservice API from Rhombus Systems — 101 operation(s) for access control integrations webservice.

GitHub OpenAPI

Operations 101

POST /api/integrations/accessControl/connectHoneywellElements Connect Honeywell Elements (validate + persist) #
POST /api/integrations/accessControl/connectHoneywellNetBox Connect Honeywell NetBox (activate) #
POST /api/integrations/accessControl/createOrUpdateHoneywellNetBoxIntegration Create or update Honeywell NetBox integration (on-prem connector) #
POST /api/integrations/accessControl/createOrUpdateHoneywellOnGuardIntegration Create or update the Honeywell OnGuard integration #
POST /api/integrations/accessControl/deleteAmtIntegration Delete AMT badge integration #
POST /api/integrations/accessControl/deleteAvigilonAltaIntegrationV2 Delete Avigilon Alta badge integration V2 #
POST /api/integrations/accessControl/deleteBoulevardIntegration Delete Boulevard integration #
POST /api/integrations/accessControl/deleteBrivoIntegration Delete Brivo badge integration #
POST /api/integrations/accessControl/deleteBrivoIntegrationV2 Delete Brivo badge integration V2 #
POST /api/integrations/accessControl/deleteButterflymxIntegration Delete ButterflyMX badge integration #
POST /api/integrations/accessControl/deleteButterflymxIntegrationV2 Delete ButterflyMX badge integration V2 #
POST /api/integrations/accessControl/deleteGeneaIntegration Delete Genea badge integration #
POST /api/integrations/accessControl/deleteGeneaIntegrationV2 Delete Genea badge integration V2 #
POST /api/integrations/accessControl/deleteHoneywellElementsIntegration Delete Honeywell Elements integration #
POST /api/integrations/accessControl/deleteHoneywellNetBoxIntegration Delete Honeywell NetBox integration #
POST /api/integrations/accessControl/deleteHoneywellOnGuardIntegration Delete Honeywell OnGuard integration #
POST /api/integrations/accessControl/deleteInnerRangeIntegration Delete Inner Range integration #
POST /api/integrations/accessControl/deleteKisiIntegration Delete Kisi badge integration #
POST /api/integrations/accessControl/deleteKisiIntegrationV2 Delete Kisi badge integration V2 #
POST /api/integrations/accessControl/deleteOpenpathIntegration Delete Openpath badge integration #
POST /api/integrations/accessControl/deleteOpentechAllianceIntegration Delete Opentech Alliance integration #
POST /api/integrations/accessControl/deleteOpentechAllianceIntegrationV2 Delete Opentech Alliance integration V2 #
POST /api/integrations/accessControl/deletePdkIntegration Delete ProDataKey badge integration #
POST /api/integrations/accessControl/deletePdkIntegrationV2 Delete ProDataKey badge integration V2 #
POST /api/integrations/accessControl/deletePlaceOsIntegration Delete PlaceOs badge integration #
POST /api/integrations/accessControl/deletePlaceOsIntegrationV2 Delete PlaceOs badge integration V2 #
POST /api/integrations/accessControl/getAmtReaders Get list of AMT readers to assign cameras #
POST /api/integrations/accessControl/getAvigilonAltaIntegration Get Avigilon Alta integration #
POST /api/integrations/accessControl/getBoulevardIntegration Get Boulevard integration #
POST /api/integrations/accessControl/getBrivoDoors Get list of available Brivo doors to assign cameras #
POST /api/integrations/accessControl/getBrivoDoorsV2 Get list of available Brivo doors to assign cameras V2 #
POST /api/integrations/accessControl/getBrivoDoorsV3 Get list of available Brivo doors to assign cameras V3 #
POST /api/integrations/accessControl/getBrivoIntegrationV2 Get Brivo badge integration V2 #
POST /api/integrations/accessControl/getButterflymxIntegrationV2 Get ButterflyMX badge integration V2 #
POST /api/integrations/accessControl/getButterflymxPanels Get list of available ButterflyMX panels to assign cameras #
POST /api/integrations/accessControl/getButterflymxPanelsV2 Get list of available ButterflyMX panels to assign cameras V2 #
POST /api/integrations/accessControl/getGeneaDoors Get list of Genea doors to assign cameras #
POST /api/integrations/accessControl/getGeneaIntegration Get Genea integration #
POST /api/integrations/accessControl/getHoneywellElementsDevices Get list of Honeywell Elements devices #
POST /api/integrations/accessControl/getHoneywellElementsIntegration Get Honeywell Elements integration #
POST /api/integrations/accessControl/getHoneywellElementsSites Get list of Honeywell Elements sites #
POST /api/integrations/accessControl/getHoneywellElementsWebhookConfig Get Honeywell Elements webhook config #
POST /api/integrations/accessControl/getHoneywellNetBoxIntegration Get Honeywell NetBox integration #
POST /api/integrations/accessControl/getHoneywellNetBoxWebhookConfig Get Honeywell NetBox webhook config #
POST /api/integrations/accessControl/getHoneywellOnGuardIntegration Get Honeywell OnGuard integration #
POST /api/integrations/accessControl/getInnerRangeConsoles Get Inner Range console settings #
POST /api/integrations/accessControl/getInnerRangeDoors Get list of Inner Range doors #
POST /api/integrations/accessControl/getInnerRangeIntegration Get Inner Range integration #
POST /api/integrations/accessControl/getKisiDoors Get list of Kisi doors to assign cameras #
POST /api/integrations/accessControl/getKisiIntegration Get Kisi badge integration #
POST /api/integrations/accessControl/getKisiIntegrationV2 Get Kisi badge integration V2 #
POST /api/integrations/accessControl/getKisiPlaces Get list of Kisi places to assign cameras #
POST /api/integrations/accessControl/getOpenpathDoors Get list of Openpath doors to assign cameras #
POST /api/integrations/accessControl/getOpenpathLockdownPlans Get list of Openpath lockdown plans to trigger #
POST /api/integrations/accessControl/getOpentechAllianceFacilities Get list of Opentech Alliance facilities #
POST /api/integrations/accessControl/getOpentechAllianceFacilitiesV2 Get list of Opentech Alliance facilities V2 #
POST /api/integrations/accessControl/getOpentechAllianceIntegrationV2 Get Opentech Alliance integration V2 #
POST /api/integrations/accessControl/getPdkDoors Get list of ProDataKey doors to assign cameras #
POST /api/integrations/accessControl/getPdkIntegration Get ProDataKey badge integration #
POST /api/integrations/accessControl/getPlaceOsDoors Get list of PlaceOs doors to assign cameras #
POST /api/integrations/accessControl/getPlaceOsIntegrationV2 Get PlaceOs integration V2 #
POST /api/integrations/accessControl/listHoneywellOnGuardIntegrations List Honeywell OnGuard deployments #
POST /api/integrations/accessControl/revertOpenpathLockdown Revert Openpath lockdown plan #
POST /api/integrations/accessControl/testBoulevardConnection Test Boulevard API connection #
POST /api/integrations/accessControl/triggerOpenpathLockdown Trigger Openpath lockdown plan #
POST /api/integrations/accessControl/unlockBrivoDoor Unlock Brivo door #
POST /api/integrations/accessControl/unlockBrivoDoorV2 Unlock Brivo door V2 #
POST /api/integrations/accessControl/unlockGeneaDoor Unlock Genea door #
POST /api/integrations/accessControl/unlockHoneywellElementsDoor Unlock Honeywell Elements door #
POST /api/integrations/accessControl/unlockHoneywellNetBoxDoor Unlock Honeywell NetBox door #
POST /api/integrations/accessControl/unlockHoneywellOnGuardDoor Unlock Honeywell OnGuard door #
POST /api/integrations/accessControl/unlockInnerRangeDoor Unlock Inner Range door #
POST /api/integrations/accessControl/unlockKisiDoor Unlock Kisi door #
POST /api/integrations/accessControl/unlockOpenpathDoor Unlock Openpath door #
POST /api/integrations/accessControl/unlockOpentechAllianceDoor Unlock Opentech Alliance door #
POST /api/integrations/accessControl/unlockOpentechAllianceDoorV2 Unlock Opentech Alliance door V2 #
POST /api/integrations/accessControl/unlockPdkDoor Unlock ProDataKey door #
POST /api/integrations/accessControl/unlockPlaceOsDoor Unlock PlaceOs door #
POST /api/integrations/accessControl/updateAmtIntegration Update AMT badge integration #
POST /api/integrations/accessControl/updateAvigilonAltaIntegrationV2 Update Avigilon Alta badge integration V2 #
POST /api/integrations/accessControl/updateBoulevardIntegration Update Boulevard integration #
POST /api/integrations/accessControl/updateBrivoIntegration Update Brivo badge integration #
POST /api/integrations/accessControl/updateBrivoIntegrationV2 Update Brivo badge integration V2 #
POST /api/integrations/accessControl/updateButterflymxIntegration Update ButterflyMX badge integration #
POST /api/integrations/accessControl/updateButterflymxIntegrationV2 Update ButterflyMX badge integration V2 #
POST /api/integrations/accessControl/updateGeneaIntegration Update Genea badge integration #
POST /api/integrations/accessControl/updateGeneaIntegrationV2 Update Genea badge integration V2 #
POST /api/integrations/accessControl/updateHoneywellElementsIntegration Update Honeywell Elements integration #
POST /api/integrations/accessControl/updateHoneywellNetBoxIntegration Update Honeywell NetBox integration #
POST /api/integrations/accessControl/updateHoneywellOnGuardIntegration Update Honeywell OnGuard behavior flags #
POST /api/integrations/accessControl/updateInnerRangeIntegration Update Inner Range integration #
POST /api/integrations/accessControl/updateKisiIntegration Update Kisi badge integration #
POST /api/integrations/accessControl/updateKisiIntegrationV2 Update Kisi badge integration V2 #
POST /api/integrations/accessControl/updateOpenpathIntegration Update Openpath badge integration #
POST /api/integrations/accessControl/updateOpentechAllianceIntegration Update Opentech Alliance integration #
POST /api/integrations/accessControl/updateOpentechAllianceIntegrationV2 Update Opentech Alliance integration V2 #
POST /api/integrations/accessControl/updatePdkIntegration Update ProDataKey badge integration #
POST /api/integrations/accessControl/updatePdkIntegrationV2 Update ProDataKey badge integration V2 #
POST /api/integrations/accessControl/updatePlaceOsSettings Update PlaceOs badge integration #
POST /api/integrations/accessControl/updatePlaceOsSettingsV2 Update PlaceOs badge integration V2 #
POST /api/integrations/accessControl/validateHoneywellElementsCredentials Validate Honeywell Elements API credentials #

Documentation

📖
Documentation
https://api-docs.rhombus.community/
📖
APIReference
https://api-docs.rhombus.community/_llms/en/api-reference.md

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/rhombus-systems/refs/heads/main/openapi/rhombus-systems-access-control-integrations-webservice-api-openapi.yml

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.
All 92 tools →

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.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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

OpenAPI Specification

rhombus-systems-access-control-integrations-webservice-api-openapi.yml Raw ↑ 
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:
      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:
      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:
      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:
      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:
      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:
      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:
      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:
      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:
      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:
      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
      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:
      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:
      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:
      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:
      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:
      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:
          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 V2
      tags:
      - Access Control Integrations Webservice
  /api/integrations/accessControl/getAmtReaders:
    post:
      operationId: getAmtReaders
      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
        sc

# --- truncated at 32 KB (279 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