Messaging
Overview
Real-time messaging: conversation CRUD, messages, members, Console settings, and a SignalR hub at /messaging/hub.
API
{pe} = /projects/{projectId}/environments/{environmentId}.
| Method | Path | Notes |
|---|---|---|
| GET | /messaging/health | Health |
| GET/PUT | /messaging{pe}/settings | Console JWT |
| POST/GET | /messaging{pe}/conversations | API key or JWT |
| GET | /messaging{pe}/conversations/{conversationId}/messages | Dual-auth |
| POST | /messaging{pe}/conversations/{conversationId}/members | Dual-auth |
| Hub | /messaging/hub | SignalR; SDK CORS |
Clients
| Package | Runtime |
|---|---|
@vijihub/messaging | dual / live (scoped messaging:live) |
VijiHub.Messaging | .NET |
Implementation
- Enable Messaging and configure settings in Console.
- Create conversations and post messages via REST with JWT or API key.
- Connect browsers to
/messaging/hubusing a scopedmessaging:livekey (or session proxy). - Add members through the members endpoint as your app model requires.
Constraints
- Settings endpoints are Console JWT only.
- Prefer scoped keys for browser live connections — not full admin keys.
- CORS must allow your app origin for the hub.
- See Authentication scoped key table.