> ## Documentation Index
> Fetch the complete documentation index at: https://api-docs.rhombus.community/llms.txt
> Use this file to discover all available pages before exploring further.

# Create or update Honeywell NetBox integration (on-prem connector)

> 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.



## OpenAPI

````yaml https://api2.rhombussystems.com/api/openapi/public.json post /api/integrations/accessControl/createOrUpdateHoneywellNetBoxIntegration
openapi: 3.0.1
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 API
  version: '1.0'
servers:
  - description: Production Server
    url: https://api2.rhombussystems.com
security:
  - ApiKeyAuth: []
paths:
  /api/integrations/accessControl/createOrUpdateHoneywellNetBoxIntegration:
    post:
      tags:
        - Access Control Integrations Webservice
      summary: Create or update Honeywell NetBox integration (on-prem connector)
      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
components:
  schemas:
    Integration_CreateOrUpdateHoneywellNetBoxIntegrationWSRequest:
      type: object
      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, while the console owns camera/location
        assignments. On first activation omit rhombusToken; the server generates
        the webhook token and returns it. On re-calls pass the token back; the
        reported door map is merged by portal key — new keys are added unmapped,
        existing keys get their display name refreshed, console-made
        camera/location/behavior assignments are never overwritten, and keys
        absent from the request (e.g. manually-added portals) are preserved.
      properties:
        baseUrl:
          type: string
          nullable: true
        doorInfoMap:
          type: object
          additionalProperties:
            $ref: '#/components/schemas/BadgeIntegrationDoorInfoType'
          nullable: true
        rhombusToken:
          type: string
          nullable: true
    Integration_CreateOrUpdateHoneywellNetBoxIntegrationWSResponse:
      type: object
      description: >-
        Result of activating/updating the Honeywell NetBox integration from the
        on-prem side. Mirrors the OnGuard response shape, minus the pre-shared
        HMAC secret (the NetBox webhook is token-only).
      properties:
        error:
          type: boolean
          nullable: true
        errorMsg:
          type: string
          nullable: true
        misconfiguredDoors:
          type: array
          items:
            type: string
            nullable: true
          nullable: true
        rhombusToken:
          type: string
          nullable: true
        warningMsg:
          type: string
          nullable: true
        webhookUrl:
          type: string
          nullable: true
    BadgeIntegrationDoorInfoType:
      type: object
      nullable: true
      properties:
        assignedCameraList:
          type: array
          items:
            type: string
            format: RUUID
            description: base 64 (url-safe) uuid string
            example: AAAAAAAAAAAAAAAAAAAAAA
            nullable: true
          nullable: true
        clipDuration:
          type: integer
          format: int32
          nullable: true
        doorName:
          type: string
          nullable: true
        leadingSeconds:
          type: integer
          format: int32
          nullable: true
        locationUuid:
          type: string
          format: RUUID
          description: base 64 (url-safe) uuid string
          example: AAAAAAAAAAAAAAAAAAAAAA
          nullable: true
        remoteUnlock:
          type: boolean
          nullable: true
        subLocationsHierarchyKey:
          type: string
          format: SubLocationsHierarchyKey
          description: |
            A sequence of one or more base 64 (url-safe) uuid substrings.
            These substrings are separated by dots (.).
          example: AAAAAAAAAAAAAAAAAAAAAA.AAAAAAAAAAAAAAAAAAAAAA.AAAAAAAAAAAAAAAAAAAAAA
          nullable: true
          pattern: ^([A-Za-z0-9\-_]{22})([.][A-Za-z0-9\-_]{22})*$
  securitySchemes:
    ApiKeyAuth:
      description: >-
        Your Rhombus API key. Must be accompanied by the `x-auth-scheme` header
        set to `api-token` (or `partner-api-token` for partner endpoints).
      in: header
      name: x-auth-apikey
      type: apiKey

````