Users & team

User availability updated

user.availability.updated

Fires when a user changes their availability status — for example, stepping away or coming back online. Useful for external operator-load dashboards.

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": "user.availability.updated",
  "event_id": "evt_01JXXXXXXXXXXXXXXXXXXXXX",
  "timestamp": "2026-03-26T12:00:00.000000Z",
  "company_id": 1,
  "data": {
    "user": {
      "id": 55,
      "name": "Aliya Seitova",
      "email": "aliya@company.kz",
      "availability": "away"
    }
  }
}

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": "user.availability.updated",
  "event_id": "evt_01JXXXXXXXXXXXXXXXXXXXXX",
  "timestamp": "2026-03-26T12:00:00.000000Z",
  "company_id": 1,
  "data": {
    "user": {
      "id": 55,
      "name": "Aliya Seitova",
      "email": "aliya@company.kz",
      "availability": "away"
    }
  }
}

Payload fields

Field	Type	Description
`user.id`	`integer`	User ID
`user.name`	`string`	Full name (first + last combined)
`user.email`	`string`	User email
`user.availability`	`string\|null`	New availability status: `online`, `away`, `offline`, or `busy`