https://livekit.io logo
Join Slack
Powered by
Is it possible to trace which API is used from Liv...
# ask-ai
b
Is it possible to trace which API is used from LiveKit Server?
✅ 1
t
Thanks for reaching out, toshi. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
Thanks — I’m responding to your question about whether you can trace which API calls are made from the LiveKit Server. Short answer: Yes. You can trace API usage from LiveKit Server using the observability features and logs available in Cloud Analytics, webhooks, and server SDK/CLI traces. What you can use to trace which API is used • Cloud Analytics / Dashboard: Session and participant pages show session events, connection metadata, and SIP call logs (when SIP is enabled). You can filter by time ranges to inspect activity that corresponds to API-driven events. • Webhooks: LiveKit emits webhook events (for example: 
room_started
, 
participant_joined
, 
track_published
, 
recording_started
, 
egress_started
). Receiving and inspecting those webhook payloads lets you map server-side events back to the API actions that caused them. Webhooks are signed so you can verify authenticity. • Server SDK and CLI tracing: Server SDK calls (Go, Node, Python, etc.) and the 
lk
CLI map directly to API endpoints. Enabling logging/tracing in your server application or the SDK will show which SDK methods / endpoints were invoked (for example, calls like 
createRoom()
or 
startRoomCompositeEgress()
). • Operational metrics & logs: LiveKit captures operational metrics and call detail records that include API interaction metadata. These metrics are retained for analysis and can help reconstruct which API calls happened during a timeframe. If you want help tracing a specific API call • Which tracing method do you prefer (Dashboard, webhooks, SDK logs, or metrics)? • Do you have a specific timeframe, room ID, or participant ID to inspect? • Are you using SIP or any server SDK (which language)? Tell me which method you want to use and share any IDs/time ranges you have, and I’ll walk you through the exact steps to locate the API calls. Sources: Data Processing Addendum | LiveKit | Say hello to improved Cloud analytics | LiveKit | Server-side | livekit/livekit_composite | DeepWiki | server-sdk-ruby | livekit/livekit_composite | DeepWiki, with interactive elements
b
Sorry, I want to know which API key is used to access LiveKit Server.
t
Thanks — I’m responding to your question about how to determine which API key was used to access the LiveKit Server. You can identify the API key by inspecting the JWT access token the client used to connect. The API key is stored in the token’s 
iss
(issuer) claim. When LiveKit validates a connection, it checks the JWT signature with the API secret that corresponds to that 
iss
value—so 
iss
is what tells you which API key was used. If you want, I can help with next steps. Which of these applies to your setup? • You have the JWT token (I can show how to decode it and find the 
iss
claim). • You only have server logs or a room/participant ID (I can suggest where to look in logs or dashboard to find the token or related event). • You’re using LiveKit Cloud or a self-hosted instance (I can tailor the steps for locating tokens/logs). Tell me which option fits and share any non-sensitive IDs or a copy of the JWT (if you’re comfortable; redact secrets). I’ll walk you through the exact steps. Sources: Server-side | livekit/livekit_composite | DeepWiki | Running LiveKit on AWS | LiveKit | Mini tutorial: setting up a LiveKit Cloud project | LiveKit | Running LiveKit on AWS | LiveKit, with interactive elements
3 Views
Open in Slack
PreviousNext
Powered by