Eliq Webhooks

# Eliq webhook catalogue — transcribed from the provider's webhook documentation.
generated: '2026-09-06'
method: searched
source: https://developer.eliq.com/doc/webhooks
provider: Eliq
providerId: eliq
docs: https://developer.eliq.com/doc/webhooks
style: outbound HTTP webhooks (Eliq POSTs to endpoints the utility implements)
transport:
  method: POST
  scheme: https (required)
  endpoint_auth: optional Basic HTTP authentication or OAuth 2.0 on the consumer endpoint
  routing: all event types may go to one endpoint, or to different endpoints per type
subscription_management:
  self_serve: false
  note: Endpoints are configured with Eliq; there is no webhook-management API in any of the four published contracts.
signature:
  header: X-Eliq-Signature
  format: t=<unix_timestamp>,sha256=<hex_hmac>
  algorithm: HMAC-SHA256
  signed_payload: '{timestamp}.{json_payload}'
  secret: shared secret generated by Eliq
  note: A new timestamp and signature are generated for every retry.
delivery:
  success: 2xx within 10 seconds
  retries: retried with decreasing frequency until a 2xx is returned or 24 hours have passed
  at_least_once: true
  dedupe: consumers MUST handle duplicates; dedupe on event.id
envelope:
  fields:
  - name: id
    type: string (uuid)
    description: Event id — the dedupe key.
  - name: created_date
    type: string (ISO 8601, UTC)
    description: When the event was created.
  - name: type
    type: string
    description: Event type; decides how `object` is parsed.
  - name: object
    type: object
    description: Type-specific payload.
  notification_inner:
  - name: location_id
    type: number
  - name: location_ext_ref
    type: string
    description: The client's own external reference for the location.
  - name: client_id
    type: number
    description: Present on market-price and connection events.
  - name: type
    type: string
    description: Notification type — the subtype column below.
  - name: object
    type: object
    description: Shape varies by notification type.
event_count: 9
events:
- type: notification_created
  subtype: budget_weekly
  group: Budgets
  description: A weekly budget completed under budget, exceeded its limit, or is forecast to exceed it.
- type: notification_created
  subtype: budget_monthly
  group: Budgets
  description: A monthly budget completed under budget, exceeded its limit, or is forecast to exceed it.
- type: notification_created
  subtype: daily_anomaly
  group: Anomalies
  description: Yesterday's consumption for a location was materially lower or higher than expected.
- type: notification_created
  subtype: monthly_anomaly
  group: Anomalies
  description: A location's consumption for the current month is unusually high.
- type: notification_created
  subtype: notifications_market_price_next_day_avg_price_alert
  group: Market price
  description: Next-day average electricity price alert. Generated and sent at 17:00 Stockholm time.
- type: notification_created
  subtype: notifications_market_price_next_day_hour_price_alert
  group: Market price
  description: Next-day hourly price peak alert. Generated and sent at 17:00 Stockholm time.
- type: notification_created
  subtype: monthly_insight
  group: Monthly report
  description: Summary of last month's energy usage, carrying localised header/content message text. Sent once the
    previous month's consumption is available for the location.
- type: notification_created
  subtype: connection_action_required
  group: Eliq Connect
  description: A meter-data connection changed state and needs the end user to act (e.g. AwaitingConfirmation ->
    Disconnected).
- type: notification_created
  subtype: connection_first_data_received
  group: Eliq Connect
  description: All connection entities have completed their first successful data sync.
asyncapi_published: false
asyncapi_note: Eliq publishes no AsyncAPI document. asyncapi/eliq-notifications-asyncapi.yml in this repo is an
  API Evangelist GENERATION from this documented catalogue, not a provider artifact.