System

Nudges updated

nudges.updated

Fires when the set of active in-app nudges for a company changes — a nudge is created from a segment action, dismissed, converted, or swept as expired. Realtime broadcast only: it is delivered over the company WebSocket (Reverb) channel and is not sent to outbound webhook subscriptions. The payload is intentionally minimal — it is a re-fetch signal, not a data carrier; clients should reload `/nudges` on receipt.

HTTP request

AISAR sends a signed POST request to your webhook_url:

http

POST {webhook_url}
Content-Type: application/json
X-AISAR-Signature: sha256=...

{
  "event": "nudges.updated",
  "event_id": "evt_01JXXXXXXXXXXXXXXXXXXXXX",
  "timestamp": "2026-06-20T12:00:00.000000Z",
  "company_id": 1,
  "data": {
    "company_id": 1
  }
}

The X-AISAR-Signature header carries an HMAC-SHA256 signature of the request body — use it to verify the request came from AISAR.

Example payload

json

{
  "event": "nudges.updated",
  "event_id": "evt_01JXXXXXXXXXXXXXXXXXXXXX",
  "timestamp": "2026-06-20T12:00:00.000000Z",
  "company_id": 1,
  "data": {
    "company_id": 1
  }
}

Payload fields

Field	Type	Description
`company_id`	`integer`	Company whose nudge set changed. Receiving clients should re-fetch `/nudges`