Skip to main content
POST
/
api
/
integrations
/
accessControl
/
connectHoneywellNetBox
Connect Honeywell NetBox (activate)
curl --request POST \
  --url https://api2.rhombussystems.com/api/integrations/accessControl/connectHoneywellNetBox \
  --header 'Content-Type: application/json' \
  --header 'x-auth-apikey: <api-key>' \
  --header 'x-auth-scheme: <x-auth-scheme>' \
  --data '
{
  "baseUrl": "<string>",
  "doorInfoMap": {}
}
'
{
  "error": true,
  "errorMsg": "<string>",
  "misconfiguredDoors": [
    "<string>"
  ],
  "rhombusToken": "<string>",
  "warningMsg": "<string>",
  "webhookUrl": "<string>"
}

Authorizations

​
x-auth-apikey
string
header
required

Your Rhombus API key. Must be accompanied by the x-auth-scheme header set to api-token (or partner-api-token for partner endpoints).

Headers

​
x-auth-scheme
enum<string>
default:api-token
required

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.

Available options:
api-token,
api,
partner-api-token,
partner-api

Body

application/json

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.

​
baseUrl
string | null
​
doorInfoMap
object

Response

200 - application/json

OK

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.

​
error
boolean | null
​
errorMsg
string | null
​
misconfiguredDoors
(string | null)[] | null
​
rhombusToken
string | null
​
warningMsg
string | null
​
webhookUrl
string | null
Last modified on June 23, 2026