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

# Get Honeywell Elements webhook config

> Returns the callback URL and suggested payload template the customer needs to paste into the Elements admin console when creating their webhook Automation. Elements does not support programmatic webhook creation, so this endpoint is the setup aid instead of a registration call.



## OpenAPI

````yaml https://api2.rhombussystems.com/api/openapi/public.json post /api/integrations/accessControl/getHoneywellElementsWebhookConfig
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/getHoneywellElementsWebhookConfig:
    post:
      tags:
        - Access Control Integrations Webservice
      summary: Get Honeywell Elements webhook config
      description: >-
        Returns the callback URL and suggested payload template the customer
        needs to paste into the Elements admin console when creating their
        webhook Automation. Elements does not support programmatic webhook
        creation, so this endpoint is the setup aid instead of a registration
        call.
      operationId: getHoneywellElementsWebhookConfig
      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_BaseIntegrationWSRequest'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: >-
                  #/components/schemas/Integration_GetHoneywellElementsWebhookConfigWSResponse
          description: OK
components:
  schemas:
    Integration_BaseIntegrationWSRequest:
      type: object
      description: Base request object for integration operations.
    Integration_GetHoneywellElementsWebhookConfigWSResponse:
      type: object
      description: >-
        Fully-formed callback URL and suggested payload template for configuring
        the webhook Automation in the Honeywell Elements admin console.
      properties:
        error:
          type: boolean
          nullable: true
        errorMsg:
          type: string
          nullable: true
        payloadTemplate:
          type: string
          nullable: true
        warningMsg:
          type: string
          nullable: true
        webhookUrl:
          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

````