curl --request POST \
--url https://api2.rhombussystems.com/api/integrations/accessControl/deleteHoneywellOnGuardIntegration \
--header 'Content-Type: application/json' \
--header 'x-auth-apikey: <api-key>' \
--header 'x-auth-scheme: <x-auth-scheme>' \
--data '{}'{
"error": true,
"errorMsg": "<string>",
"warningMsg": "<string>"
}Delete Honeywell OnGuard integration. Callable from the Rhombus console (admin) or from the OnGuard side (uninstall).
curl --request POST \
--url https://api2.rhombussystems.com/api/integrations/accessControl/deleteHoneywellOnGuardIntegration \
--header 'Content-Type: application/json' \
--header 'x-auth-apikey: <api-key>' \
--header 'x-auth-scheme: <x-auth-scheme>' \
--data '{}'{
"error": true,
"errorMsg": "<string>",
"warningMsg": "<string>"
}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.
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?