The VideoKit object is automatically initialized on application start-up, but in order to communicate with our servers, you will need to start a session using your Video.io API token.
As said, a session should be created before using any other Video.io API that communicates with our servers. What is the right moment to start a session?
- If your app has no login system, the session can be safely started in
- If users login into your app, the session should be bound to the login lifecycle. In other words, you can start a Video.io session whenever you know the user identifier.
Sessions are started through the session manager (
VideoKit.sessions()) and require you to pass
the API token and an identifier of the current logged in user. This identifier is extremely
important because performing certain operations on videos require a session that uses the same
identifier with which the video was created for the first time.
As you can see, the start() method returns a
Call object described here.
To clear the current session, simply call
To access the current session, simply call
get(). You can also add and remove session listeners,
which are useful in certain cases.