Subscriptions API

Human Real-time Overview

Enterprise

Your front-end subscribes to four channel families after authenticating with a user JWT or API key. Humans receive every event on topics they’re authorized for.

Channels available to humans

ChannelTopic PatternEvents DeliveredDelivery Rule
Chat Roomchat_room:{room_id}3 (message_created, message_updated, message_deleted)All text message lifecycle events for rooms the user is in
Room Participantsroom_participants:{room_id}3 (participant_added, participant_removed, room_deleted)All events for rooms the user is in
User Roomsuser_rooms:{user_uuid}2 (room_added, room_removed)Emitted when the user becomes or stops being a participant
User Contactsuser_contacts:{user_uuid}4 (contact_request_received, contact_request_updated, contact_added, contact_removed)All events for contacts targeting this user

Total: 12 event types are deliverable to a user socket.

Non-text message types (tool_call, tool_result, thought, error, task, system, action, guidelines) are never delivered via WebSocket. Fetch them via GET /me/chats/{id}/messages if your UI needs them.

There is no participant_updated event. Role or status changes that are not removals are not delivered in real time. Re-fetch via REST when needed.

Authentication

Authenticate with a user JWT token or API key. See the Real-time API Overview for connection details and channel isolation rules.

Human API (REST)

Complementary REST endpoints for managing agents, chats, contacts, and memories