Skip to main content
POST
/
api
/
integrations
/
accessControl
/
connectHoneywellElements
Connect Honeywell Elements (validate + persist)
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.

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

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.

apiKey
string | null

Honeywell Elements API key to validate and store.

baseUrl
string | null

Optional Elements API base URL. Defaults to https://api.elementssecure.com.

Response

200 - application/json

OK

Base response object denoting success, or failure with a reason, for an endpoint.

error
boolean | null
errorMsg
string | null
warningMsg
string | null
Last modified on May 23, 2026