Nextcloud Talk API documentation
3.0 (Initial Talk release)
audio - audio is supported
video - video + screensharing is supported
chat - simple text chat is supported, superseded by
guest-signaling - Guests can do signaling via api endpoints
empty-group-room - Group conversations can be created without inviting a Nextcloud user group by default
guest-display-names - Display names of guests are stored in the database, can be set via API (not WebRTC only) and are used on returned comments/participants/etc.
multi-room-users - Users can be in multiple conversations at the same time now, therefor signaling now also requires the conversation token on the URL.
chat-v2 - Chat messages are now
Rich Object Strings and pagination is available, the previous
chat is not available anymore.
favorites - Conversations can be marked as favorites which will pin them to the top of the conversation list.
last-room-activity - Conversations have the
lastActivity attribute and should be sorted by that instead of the last ping of the user.
no-ping - The ping endpoint has been removed. Ping is updated with a call to fetch the signaling or chat messages instead.
system-messages - Chat messages have a
systemMessage attribute and can be generated by the system
mention-flag - The conversation list populates the boolean
unreadMention when the user was mentioned since their last visit
in-call-flags - A new flag
participantFlags has been introduced and is replacing the
Replaced by Guests can be invited with their email address
notification-levels - Users can select when they want to be notified in conversations
invite-groups-and-mails - Groups can be added to existing conversations via the add participant endpoint
locked-one-to-one-rooms - One-to-one conversations are now locked to the users. Neither guests nor other participants can be added, so the options to do that should be hidden as well. Also a user can only leave a one-to-one conversation (not delete). It will be deleted when the other participant left too. If the other participant posts a new chat message or starts a call, the left-participant will be re-added.
read-only-rooms - Conversations can be in
read-only mode which means people can not do calls or write chat messages.
chat-read-marker - The chat can be optionally marked read by clients manually, independent from the loading of the chat messages.
webinary-lobby - See
Webinary management for technical details.
start-call-flag - Only moderators or users might be able to start calls.
chat-replies - Normal chat messages can now be replied to. Check the
isReplyable parameter on the message object.
circles-support - Conversations can be created for circles and all circle members can be added to existing conversations
config => attachments => allowed - Whether the user can upload files into a chat
config => attachments => folder - User defined folder where items should be uploaded to
config => conversations => can-create - Whether the user can create public and group conversations, if not only one-to-one conversations are allowed
force-mute - "forceMute" signaling messages can be sent to mute other participants.
conversation-v2 - The conversations API v2 is less load heavy and should be used by clients when available. Check the difference in the
Conversation API documentation.
chat-reference-id - an optional referenceId can be sent with a chat message to be able to identify it in parallel get requests to earlier fade out a temporary message