Thanks — that's helpful. You're asking whether LiveKit supports Token-Oriented Object Notation (TOON).
TOON is not mentioned in our information, so LiveKit does not have built‑in support for a format specifically named TOON.
If your goal is to exchange structured data alongside LiveKit sessions (for example, signaling, metadata, or application messages), here are ways you can accomplish similar outcomes:
• Use LiveKit's DataChannels to send arbitrary serialized payloads between participants. You can serialize your TOON messages to bytes or strings and transmit them over a DataChannel.
• Attach metadata to participants or tracks where appropriate (for small pieces of data) and update/read that metadata from your application.
• If you need server-side processing or storage of TOON messages, send them from clients to your application server (over HTTP/WebSocket), process or persist them there, and forward relevant updates through LiveKit DataChannels or REST APIs.
If you want, tell me:
• How you plan to use TOON with LiveKit (signaling, state sync, message history, etc.), and
• Which SDK/platform you’re using (browser, iOS, Android, or server).
I can then suggest a concrete integration pattern and example payload handling.