Rhombus Systems

Rhombus Systems Component Webservice API

The Component Webservice API from Rhombus Systems — 62 operation(s) for component webservice.

GitHub OpenAPI

Operations 62

POST /api/component/addAccessControlledDoorLabel Create a label that can be assigned to an access controlled door #
POST /api/component/createAccessControlledDoor Create an access controlled door #
POST /api/component/createAccessControlledDoorSeekpoints Create custom activity seekpoints for a specified access controlled door #
POST /api/component/createIntegratedDoorPositionIndicator Create a door position indicator component #
POST /api/component/createIntegratedDoorRelay Create a door relay component #
POST /api/component/createIntegratedGenericButton Create a generic button component #
POST /api/component/createIntegratedGenericInput Create a generic input component #
POST /api/component/createIntegratedGenericRelay Create a generic relay component #
POST /api/component/createIntegratedRequestToExit Create a request to exit component #
POST /api/component/createOsdpDoorReader Create a third party OSDP Reader component #
POST /api/component/createRhombusOsdpDoorReader Create a Rhombus OSDP Reader component #
POST /api/component/createWiegandReader Create a third party Wiegand Reader component #
POST /api/component/deleteAccessControlledDoor Delete the specified access controlled door #
POST /api/component/deleteComponent Delete a component #
POST /api/component/deleteComponentsByOwnerDevice Delete all components owned by the specified device #
POST /api/component/findAccessControlledDoorShadows Find access controlled door shadows within the org #
POST /api/component/findAccessControlledDoorShadowsByLocation Find access controlled door shadows within the specified location #
POST /api/component/findAccessControlledDoors Find access controlled doors within the org #
POST /api/component/findAccessControlledDoorsByLocation Find access controlled doors within the specified location #
POST /api/component/findAccessControlledDoorsByOwnerDevice Find access controlled doors for the specified owner device #
POST /api/component/findAllComponentShadows Retrieve all component shadows for the specified component uuids #
POST /api/component/findComponentEventsByAccessControlledDoor Retrieve all component events relevant to the specified AccessControlledDoor #
POST /api/component/findComponentEventsByApiToken Retrieve all component events relevant to the specified api token #
POST /api/component/findComponentEventsByComponent Retrieve all component events relevant to the specified component #
POST /api/component/findComponentEventsByCorrelation Retrieve all component events relevant to the specified correlation id #
POST /api/component/findComponentEventsByCredentialHexValue Retrieve all component events relevant to the specified credential hex value #
POST /api/component/findComponentEventsByCredentialUuid Retrieve all component events relevant to the specified credential uuid #
POST /api/component/findComponentEventsByCredentialValue Retrieve all component events relevant to the specified credential value #
POST /api/component/findComponentEventsByGuestPass Retrieve all component events relevant to the specified guest pass #
POST /api/component/findComponentEventsByLocation Retrieve all component events relevant to the specified location #
POST /api/component/findComponentEventsByOwnerDevice Retrieve all component events relevant to the specified owner device… #
POST /api/component/findComponentEventsBySupportAuthority Retrieve all component events relevant to the specified support authority #
POST /api/component/findComponentEventsByUser Retrieve all component events relevant to the specified User #
POST /api/component/findComponentEventsForVideoIntercom Retrieve all component events relevant to the specified Video Intercom and… #
POST /api/component/findComponentSeekPointsByAccessControlledDoor Find component seekpoints by access controlled door #
POST /api/component/findComponentSeekPointsByAccessControlledDoors Find component seekpoints by access controlled doors #
POST /api/component/findComponentSeekPointsByComponent Find component seekpoints by component #
POST /api/component/findComponentSeekPointsByLocation Find component seekpoints by location #
POST /api/component/findComponentSeekPointsByOwnerDevice Find component seekpoints by owner device #
POST /api/component/findComponentSeekPointsByUser Find component seekpoints by user #
POST /api/component/findComponentShadowsByComponentComposites Retrieve all component shadows for the components belonging to the specified… #
POST /api/component/findComponentShadowsByOwnerDevice Retrieve component shadows by the specified owner device uuid #
POST /api/component/findComponentsByOwnerDevice Retrieve a list of components owned by a Rhombus device #
POST /api/component/findMinimalStateAccessControlledDoors Find minimal state access controlled doors within the org #
POST /api/component/findMinimalStateAccessControlledDoorsByLocation Find minimal state access controlled doors within the specified location #
POST /api/component/findPaginatedComponentEventsByAccessControlledDoor Retrieve all component events relevant to the specified AccessControlledDoor #
POST /api/component/findPaginatedComponentEventsByOwnerDevice Retrieve all component events relevant to the specified owner device #
POST /api/component/getAccessControlledDoorLabelsForOrg Get all access controlled door labels for the organization #
POST /api/component/getOrCreateDevicePhysicalPortConfig Get or create device physical port config #
POST /api/component/removeAccessControlledDoorLabel Remove a label to an access controlled door #
POST /api/component/updateAccessControlledDoor Updates an access controlled door #
POST /api/component/updateIntegratedDoorPositionIndicator Update a door position indicator component #
POST /api/component/updateIntegratedDoorRelay Update a door relay component #
POST /api/component/updateIntegratedGenericButton Update a generic button component #
POST /api/component/updateIntegratedGenericInput Update a generic input component #
POST /api/component/updateIntegratedGenericRelay Update a generic relay component #
POST /api/component/updateIntegratedGenericRelaySteadyState Update a generic relay component's steady state #
POST /api/component/updateIntegratedGenericRelayTransientState Activate a generic relay for a brief period #
POST /api/component/updateIntegratedRequestToExit Update a request to exit component #
POST /api/component/updateOsdpDoorReader Update a third party OSDP Reader component #
POST /api/component/updateRhombusOsdpDoorReader Update a Rhombus OSDP Reader component #
POST /api/component/updateWiegandDoorReader Update a third party Wiegand Reader component #

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-component-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-component-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-component-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 Component Webservice API
  version: '1.0'
servers:
- description: Production Server
  url: https://api2.rhombussystems.com
security:
- ApiKeyAuth: []
tags:
- name: Component Webservice
paths:
  /api/component/addAccessControlledDoorLabel:
    post:
      description: Create a label that can be assigned to an access controlled door and referenced by an access grant or access revocation
      operationId: addAccessControlledDoorLabel
      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/Component_AddAccessControlledDoorLabelWSRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Component_AddAccessControlledDoorLabelWSResponse'
          description: OK
      summary: Create a label that can be assigned to an access controlled door
      tags:
      - Component Webservice
  /api/component/createAccessControlledDoor:
    post:
      operationId: createAccessControlledDoor
      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/Component_CreateAccessControlledDoorWSRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Component_CreateAccessControlledDoorWSResponse'
          description: OK
      summary: Create an access controlled door
      tags:
      - Component Webservice
  /api/component/createAccessControlledDoorSeekpoints:
    post:
      operationId: createAccessControlledDoorSeekpoints
      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/Component_CreateAccessControlledDoorSeekpointsWSRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Component_CreateAccessControlledDoorSeekpointsWSResponse'
          description: OK
      summary: Create custom activity seekpoints for a specified access controlled door
      tags:
      - Component Webservice
  /api/component/createIntegratedDoorPositionIndicator:
    post:
      operationId: createIntegratedDoorPositionIndicator
      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/Component_CreateIntegratedDoorPositionIndicatorWSRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Component_CreateIntegratedDoorPositionIndicatorWSResponse'
          description: OK
      summary: Create a door position indicator component
      tags:
      - Component Webservice
  /api/component/createIntegratedDoorRelay:
    post:
      operationId: createIntegratedDoorRelay
      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/Component_CreateIntegratedDoorRelayWSRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Component_CreateIntegratedDoorRelayWSResponse'
          description: OK
      summary: Create a door relay component
      tags:
      - Component Webservice
  /api/component/createIntegratedGenericButton:
    post:
      operationId: createIntegratedGenericButton
      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/Component_CreateIntegratedGenericButtonWSRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Component_CreateIntegratedGenericButtonWSResponse'
          description: OK
      summary: Create a generic button component
      tags:
      - Component Webservice
  /api/component/createIntegratedGenericInput:
    post:
      operationId: createIntegratedGenericInput
      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/Component_CreateIntegratedGenericInputWSRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Component_CreateIntegratedGenericInputWSResponse'
          description: OK
      summary: Create a generic input component
      tags:
      - Component Webservice
  /api/component/createIntegratedGenericRelay:
    post:
      operationId: createIntegratedGenericRelay
      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/Component_CreateIntegratedGenericRelayWSRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Component_CreateIntegratedGenericRelayWSResponse'
          description: OK
      summary: Create a generic relay component
      tags:
      - Component Webservice
  /api/component/createIntegratedRequestToExit:
    post:
      operationId: createIntegratedRequestToExit
      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/Component_CreateIntegratedRequestToExitWSRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Component_CreateIntegratedRequestToExitWSResponse'
          description: OK
      summary: Create a request to exit component
      tags:
      - Component Webservice
  /api/component/createOsdpDoorReader:
    post:
      operationId: createOsdpDoorReader
      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/Component_CreateOsdpReaderWSRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Component_CreateOsdpReaderWSResponse'
          description: OK
      summary: Create a third party OSDP Reader component
      tags:
      - Component Webservice
  /api/component/createRhombusOsdpDoorReader:
    post:
      operationId: createRhombusOsdpDoorReader
      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/Component_CreateRhombusOsdpReaderWSRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Component_CreateRhombusOsdpReaderWSResponse'
          description: OK
      summary: Create a Rhombus OSDP Reader component
      tags:
      - Component Webservice
  /api/component/createWiegandReader:
    post:
      operationId: createWiegandReader
      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/Component_CreateWiegandReaderWSRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Component_CreateWiegandReaderWSResponse'
          description: OK
      summary: Create a third party Wiegand Reader component
      tags:
      - Component Webservice
  /api/component/deleteAccessControlledDoor:
    post:
      operationId: deleteAccessControlledDoor
      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/Component_DeleteAccessControlledDoorWSRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Component_DeleteAccessControlledDoorWSResponse'
          description: OK
      summary: Delete the specified access controlled door
      tags:
      - Component Webservice
  /api/component/deleteComponent:
    post:
      operationId: deleteComponent
      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/Component_DeleteComponentWSRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Component_DeleteComponentWSResponse'
          description: OK
      summary: Delete a component
      tags:
      - Component Webservice
  /api/component/deleteComponentsByOwnerDevice:
    post:
      operationId: deleteComponentsByOwnerDevice
      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/Component_DeleteComponentsByOwnerDeviceWSRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Component_DeleteComponentsByOwnerDeviceWSResponse'
          description: OK
      summary: Delete all components owned by the specified device
      tags:
      - Component Webservice
  /api/component/findAccessControlledDoorShadows:
    post:
      operationId: findAccessControlledDoorShadows
      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/Component_FindAccessControlledDoorShadowsWSRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Component_FindAccessControlledDoorShadowsWSResponse'
          description: OK
      summary: Find access controlled door shadows within the org
      tags:
      - Component Webservice
  /api/component/findAccessControlledDoorShadowsByLocation:
    post:
      operationId: findAccessControlledDoorShadowsByLocation
      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/Component_FindAccessControlledDoorShadowsByLocationWSRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Component_FindAccessControlledDoorShadowsByLocationWSResponse'
          description: OK
      summary: Find access controlled door shadows within the specified location
      tags:
      - Component Webservice
  /api/component/findAccessControlledDoors:
    post:
      operationId: findAccessControlledDoors
      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/Component_FindAccessControlledDoorsWSRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Component_FindAccessControlledDoorsWSResponse'
          description: OK
      summary: Find access controlled doors within the org
      tags:
      - Component Webservice
  /api/component/findAccessControlledDoorsByLocation:
    post:
      operationId: findAccessControlledDoorsByLocation
      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/Component_FindAccessControlledDoorsByLocationWSRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Component_FindAccessControlledDoorsByLocationWSResponse'
          description: OK
      summary: Find access controlled doors within the specified location
      tags:
      - Component Webservice
  /api/component/findAccessControlledDoorsByOwnerDevice:
    post:
      operationId: findAccessControlledDoorsByOwnerDevice
      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/Component_FindAccessControlledDoorsByOwnerDeviceWSRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Component_FindAccessControlledDoorsByOwnerDeviceWSResponse'
          description: OK
      summary: Find access controlled doors for the specified owner device
      tags:
      - Component Webservice
  /api/component/findAllComponentShadows:
    post:
      operationId: findAllComponentShadows
      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/Component_FindAllComponentShadowsWSRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Component_FindAllComponentShadowsWSResponse'
          description: OK
      summary: Retrieve all component shadows for the specified component uuids
      tags:
      - Component Webservice
  /api/component/findComponentEventsByAccessControlledDoor:
    post:
      operationId: findComponentEventsByAccessControlledDoor
      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/Component_FindComponentEventsByAccessControlledDoorWSRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Component_FindComponentEventsByAccessControlledDoorWSResponse'
          description: OK
      summary: Retrieve all component events relevant to the specified AccessControlledDoor
      tags:
      - Component Webservice
  /api/component/findComponentEventsByApiToken:
    post:
      operationId: findComponentEventsByApiToken
      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/Component_FindComponentEventsByApiTokenWSRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Component_FindComponentEventsByApiTokenWSResponse'
          description: OK
      summary: Retrieve all component events relevant to the specified api token
      tags:
      - Component Webservice
  /api/component/findComponentEventsByComponent:
    post:
      operationId: findComponentEventsByComponent
      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/Component_FindComponentEventsByComponentWSRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Component_FindComponentEventsByComponentWSResponse'
          description: OK
      summary: Retrieve all component events relevant to the specified component
      tags:
      - Component Webservice
  /api/component/findComponentEventsByCorrelation:
    post:
      operationId: findComponentEventsByCorrelation
      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/Component_FindComponentEventsByCorrelationWSRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Component_FindComponentEventsByCorrelationWSResponse'
          description: OK
      summary: Retrieve all component events relevant to the specified correlation id
      tags:
      - Component Webservice
  /api/component/findComponentEventsByCredentialHexValue:
    post:
      operationId: findComponentEventsByCredentialHexValue
      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/Component_FindComponentEventsByCredentialHexValueWSRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Component_FindComponentEventsByCredentialHexValueWSResponse'
          description: OK
      summary: Retrieve all component events relevant to the specified credential hex value
      tags:
      - Component Webservice
  /api/component/findComponentEventsByCredentialUuid:
    post:
      operationId: findComponentEventsByCredentialUuid
      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/Component_FindComponentEventsByCredentialUuidWSRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Component_FindComponentEventsByCredentialUuidWSResponse'
          description: OK
      summary: Retrieve all component events relevant to the specified credential uuid
      tags:
      - Component Webservice
  /api/component/findComponentEventsByCredentialValue:
    post:
      operationId: findComponentEventsByCredentialValue
      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/Component_FindComponentEventsByCredentialValueWSRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
              

# --- truncated at 32 KB (290 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/rhombus-systems/refs/heads/main/openapi/rhombus-systems-component-webservice-api-openapi.yml