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

# Connect Honeywell NetBox (activate)

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



## OpenAPI

````yaml https://api2.rhombussystems.com/api/openapi/public.json post /api/integrations/accessControl/connectHoneywellNetBox
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/connectHoneywellNetBox:
    post:
      tags:
        - Access Control Integrations Webservice
      summary: Connect Honeywell NetBox (activate)
      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
components:
  schemas:
    Integration_ConnectHoneywellNetBoxWSRequest:
      type: object
      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, omit any token; the server
        generates a webhook rhombusToken and returns it (plus the fully-formed
        webhook URL) for the customer to paste into the NetBox webhook
        forwarder. Subsequent calls preserve the existing token so the
        configured forwarder keeps working as the door mapping changes. The
        request owns the door mapping; map keys are the stable NetBox portal
        identifiers and values follow the standard Rhombus badge-integration
        door info shape.
      properties:
        baseUrl:
          type: string
          nullable: true
        doorInfoMap:
          type: object
          additionalProperties:
            $ref: '#/components/schemas/BadgeIntegrationDoorInfoType'
          nullable: true
    Integration_ConnectHoneywellNetBoxIntegrationWSResponse:
      type: object
      description: >-
        Result of activating or updating the Honeywell NetBox integration.
        Returns the webhook URL and token to configure on the NetBox webhook
        forwarder. The token is stable across re-calls so the configured
        forwarder keeps working when the door mapping changes.
      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

````