🚧 The Rhombus Developer Documentation is currently in beta. For the official documentation, please visit docs.rhombus.com.
curl --request POST \
--url https://api2.rhombussystems.com/api/integrations/accessControl/getHoneywellNetBoxWebhookConfig \
--header 'Content-Type: application/json' \
--header 'x-auth-apikey: <api-key>' \
--header 'x-auth-scheme: <x-auth-scheme>' \
--data '{}'{
"error": true,
"errorMsg": "<string>",
"payloadTemplate": "<string>",
"warningMsg": "<string>",
"webhookUrl": "<string>"
}Stubbed setup aid for the upcoming Honeywell NetBox integration. Returns a placeholder webhook URL and payload template so the frontend can be wired end-to-end before the backend integration (types, gateway, webhook engine) is implemented.
curl --request POST \
--url https://api2.rhombussystems.com/api/integrations/accessControl/getHoneywellNetBoxWebhookConfig \
--header 'Content-Type: application/json' \
--header 'x-auth-apikey: <api-key>' \
--header 'x-auth-scheme: <x-auth-scheme>' \
--data '{}'{
"error": true,
"errorMsg": "<string>",
"payloadTemplate": "<string>",
"warningMsg": "<string>",
"webhookUrl": "<string>"
}Your Rhombus API key. Must be accompanied by the x-auth-scheme header set to api-token (or partner-api-token for partner endpoints).
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.
api-token, api, partner-api-token, partner-api Base request object for integration operations.
Was this page helpful?