> ## 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.

# Connect Honeywell Elements (validate + persist)

> 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.



## OpenAPI

````yaml https://api2.rhombussystems.com/api/openapi/public.json post /api/integrations/accessControl/connectHoneywellElements
openapi: 3.0.1
info:
  contact:
    email: developer@rhombussystems.com
  description: >-
    This API is for use by Rhombus customers and partners.


    ## Authentication


    All requests require two headers:

    - `x-auth-scheme` — The authentication scheme identifier. Use `api-token`
    for standard API key auth, or `partner-api-token` for partner API auth.

    - `x-auth-apikey` — Your Rhombus API key.


    Example:

    ```

    POST /api/camera/getMinimalCameraStateList

    x-auth-scheme: api-token

    x-auth-apikey: YOUR_API_KEY

    Content-Type: application/json

    ```
  title: Rhombus API
  version: '1.0'
servers:
  - description: Production Server
    url: https://api2.rhombussystems.com
security:
  - ApiKeyAuth: []
paths:
  /api/integrations/accessControl/connectHoneywellElements:
    post:
      tags:
        - Access Control Integrations Webservice
      summary: Connect Honeywell Elements (validate + persist)
      description: >-
        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.
      operationId: connectHoneywellElements
      parameters:
        - description: >-
            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.
          example: api-token
          in: header
          name: x-auth-scheme
          required: true
          schema:
            type: string
            default: api-token
            enum:
              - api-token
              - api
              - partner-api-token
              - partner-api
      requestBody:
        content:
          application/json:
            schema:
              $ref: >-
                #/components/schemas/Integration_ConnectHoneywellElementsWSRequest
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BaseApiResponse'
          description: OK
components:
  schemas:
    Integration_ConnectHoneywellElementsWSRequest:
      type: object
      description: >-
        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.
      properties:
        apiKey:
          type: string
          description: Honeywell Elements API key to validate and store.
          nullable: true
        baseUrl:
          type: string
          description: >-
            Optional Elements API base URL. Defaults to
            https://api.elementssecure.com.
          nullable: true
    BaseApiResponse:
      type: object
      description: >-
        Base response object denoting success, or failure with a reason, for an
        endpoint.
      properties:
        error:
          type: boolean
          nullable: true
        errorMsg:
          type: string
          nullable: true
        warningMsg:
          type: string
          nullable: true
  securitySchemes:
    ApiKeyAuth:
      description: >-
        Your Rhombus API key. Must be accompanied by the `x-auth-scheme` header
        set to `api-token` (or `partner-api-token` for partner endpoints).
      in: header
      name: x-auth-apikey
      type: apiKey

````