curl --request POST \
--url https://api2.rhombussystems.com/api/integrations/accessControl/connectHoneywellElements \
--header 'Content-Type: application/json' \
--header 'x-auth-apikey: <api-key>' \
--header 'x-auth-scheme: <x-auth-scheme>' \
--data '
{
"apiKey": "<string>",
"baseUrl": "<string>"
}
'{
"error": true,
"errorMsg": "<string>",
"warningMsg": "<string>"
}Step 1 of the Elements setup wizard: validate the API key against Honeywell Elements and persist on success. After this call, subsequent endpoints (sites, devices, update) resolve credentials from the stored row and never require the API key again.
curl --request POST \
--url https://api2.rhombussystems.com/api/integrations/accessControl/connectHoneywellElements \
--header 'Content-Type: application/json' \
--header 'x-auth-apikey: <api-key>' \
--header 'x-auth-scheme: <x-auth-scheme>' \
--data '
{
"apiKey": "<string>",
"baseUrl": "<string>"
}
'{
"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 Step 1 of the Elements setup wizard: validate the API key against Honeywell Elements and persist on success. Subsequent endpoints (sites, devices, update) resolve credentials from the stored row and never require the API key again.
Honeywell Elements API key to validate and store.
Optional Elements API base URL. Defaults to https://api.elementssecure.com.
Was this page helpful?