---
title: "network.presence.changed@1 · OpenVibe.Services"
canonical: "https://openvibe.services/docs/contracts/network.presence.changed"
updated: null
---

# network.presence.changed@1 · OpenVibe.Services

HTML: [network.presence.changed@1 · OpenVibe.Services](https://openvibe.services/docs/contracts/network.presence.changed)

# NetworkPresenceChangedPayload `network.presence.changed@1`

Generated at 2026-11-13 06:25:48 UTC from [`openvibe-contracts v0.419.0`](https://github.com/OpenVibers/OpenVibe.Contracts/tree/v0.419.0) and [`openvibe-sdk v0.161.0`](https://github.com/OpenVibers/OpenVibe.SDK/tree/v0.161.0).

- Version: 1.0.0
- Owner: network
- Visibility: first-party
- Status: active
- Compatibility: backward
- Schema: [`https://openvibe.network/contracts/events/payloads/network.presence.changed.v1.json`](/docs/contracts/network.presence.changed.json)

network.presence.changed v1 (OpenVibe.Network server/presence; plan 2026-10-22 track X item 9). A person's public presence changed: their chosen state, status line, emoji, the show\_status switch, or the derived online/away/offline state. OpenVibe.Network writes it to its outbox beside the presence row, at most once per person per 30 seconds (the debounce), and only for a real change. The payload is the public view in network.presence@1: invisible and show\_status off are sent as offline with no status text or emoji, so the event never carries what the person hid. Envelope: subject { type: user, id: <usr\_…> }, visibility internal, actor the person. A presence change is not a reason to notify anyone.

## Fields

| Field | Type | Required | Description | Constraints |
| --- | --- | --- | --- | --- |
| `subject` | string | yes |  | - `pattern ^usr_[0-9A-HJKMNP-TV-Z]{26}$` |
| `state` | enum | yes | The public state. Never invisible: an invisible person is sent as offline, without their status text or emoji. | - `one of "online", "away", "dnd", "offline"` |
| `status_text` | string \| null |  |  | - `maxLength 80` |
| `emoji` | string \| null |  |  | - `maxLength 16` |
| `live` | boolean |  | Streaming on OpenVibe.Live now; false while invisible or with show\_status off. | - `default false` |
| `updated_at` | string | yes |  | - `format date-time` |

## Examples

From the contract's own test fixtures: valid ones validate, rejected ones must fail.

 Valid: offline

~~~~
{
  "subject": "usr_01JAB2C3D4E5F6G7H8J9K0MNPQ",
  "state": "offline",
  "status_text": null,
  "emoji": null,
  "live": false,
  "updated_at": "2026-11-07T09:00:00.000Z"
}
~~~~

Valid: online

~~~~
{
  "subject": "usr_01JAB2C3D4E5F6G7H8J9K0MNPQ",
  "state": "online",
  "status_text": "Building presence",
  "emoji": "🟢",
  "live": true,
  "updated_at": "2026-11-07T09:00:00.000Z"
}
~~~~

Rejected: bad-subject

~~~~
{
  "subject": "ann",
  "state": "online",
  "updated_at": "2026-11-07T09:00:00.000Z"
}
~~~~

Rejected: invisible

~~~~
{
  "subject": "usr_01JAB2C3D4E5F6G7H8J9K0MNPQ",
  "state": "invisible",
  "updated_at": "2026-11-07T09:00:00.000Z"
}
~~~~

## Validate

~~~~
const contracts = require('openvibe-contracts');
contracts.validate('network.presence.changed@1', value);   // { valid, errors: [{ path, message }] }
~~~~