jitsi-meet/doc/api.md

Jitsi Meet API

You can use the Jitsi Meet API to embed Jitsi Meet in to your application. You are also welcome to use it for embedding the globally distributed and highly available deployment on meet.jit.si itself. The only thing we ask for in that case is that you please DO NOT remove the jitsi.org logo from the top left corner.

Installation

To embed Jitsi Meet in your application you need to add the Jitsi Meet API library:

<script src='https://meet.jit.si/external_api.js'></script>

API

api = new JitsiMeetExternalAPI(domain, options)

The next step for embedding Jitsi Meet is to create the Jitsi Meet API object. Its constructor gets a number of options:

• domain: domain used to build the conference URL, 'meet.jit.si' for example.
• options: object with properties - the optional arguments:
  • roomName: (optional) name of the room to join.
  • width: (optional) width for the iframe which will be created. If a number is specified it's treated as pixel units. If a string is specified the format is number followed by 'px', 'em', 'pt' or '%'.
  • height: (optional) height for the iframe which will be created. If a number is specified it's treated as pixel units. If a string is specified the format is number followed by 'px', 'em', 'pt' or '%'.
  • parentNode: (optional) HTML DOM Element where the iframe will be added as a child.
  • configOverwrite: (optional) JS object with overrides for options defined in config.js.
  • interfaceConfigOverwrite: (optional) JS object with overrides for options defined in interface_config.js.
  • noSSL: (optional, defaults to true) Boolean indicating if the server should be contacted using HTTP or HTTPS.
  • jwt: (optional) JWT token.
  • onload: (optional) handler for the iframe onload event.
  • invitees: (optional) Array of objects containing information about new participants that will be invited in the call.
  • devices: (optional) A map containing information about the initial devices that will be used in the call.
  • userInfo: (optional) JS object containing information about the participant opening the meeting, such as email.

Example:

const domain = 'meet.jit.si';
const options = {
    roomName: 'JitsiMeetAPIExample',
    width: 700,
    height: 700,
    parentNode: document.querySelector('#meet')
};
const api = new JitsiMeetExternalAPI(domain, options);

You can set the initial media devices for the call:

const domain = 'meet.jit.si';
const options = {
    ...
    devices: {
        audioInput: '<deviceLabel>',
        audioOutput: '<deviceLabel>',
        videoInput: '<deviceLabel>'
    },
    ...
};
const api = new JitsiMeetExternalAPI(domain, options);

You can overwrite options set in config.js and interface_config.js. For example, to enable the filmstrip-only interface mode, you can use:

const options = {
    ...
    interfaceConfigOverwrite: { filmStripOnly: true },
    ...
};
const api = new JitsiMeetExternalAPI(domain, options);

You can also pass a jwt token to Jitsi Meet:

const options = {
   ...
   jwt: '<jwt_token>',
   noSsl: false,
   ...
};
const api = new JitsiMeetExternalAPI(domain, options);

You can set the userInfo(email) for the call:

var domain = "meet.jit.si";
var options = {
    ...
    userInfo: {
        email: 'email@jitsiexamplemail.com'
    }
}
var api = new JitsiMeetExternalAPI(domain, options);

Controlling the embedded Jitsi Meet Conference

Device management JitsiMeetExternalAPI methods:

• getAvailableDevices - Retrieve a list of available devices.

api.getAvailableDevices().then(devices => {
    // devices = {
    //     audioInput: [{
    //         deviceId: 'ID'
    //         groupId: 'grpID'
    //         kind: 'audioinput'
    //         label: 'label'
    //     },....],
    //     audioOutput: [{
    //         deviceId: 'ID'
    //         groupId: 'grpID'
    //         kind: 'audioOutput'
    //         label: 'label'
    //     },....],
    //     videoInput: [{
    //         deviceId: 'ID'
    //         groupId: 'grpID'
    //         kind: 'videoInput'
    //         label: 'label'
    //     },....]
    // }
    ...
});

• getCurrentDevices - Retrieve a list with the devices that are currently selected.

api.getCurrentDevices().then(devices => {
    // devices = {
    //     audioInput: {
    //         deviceId: 'ID'
    //         groupId: 'grpID'
    //         kind: 'videoInput'
    //         label: 'label'
    //     },
    //     audioOutput: {
    //         deviceId: 'ID'
    //         groupId: 'grpID'
    //         kind: 'videoInput'
    //         label: 'label'
    //     },
    //     videoInput: {
    //         deviceId: 'ID'
    //         groupId: 'grpID'
    //         kind: 'videoInput'
    //         label: 'label'
    //     }
    // }
    ...
});

• isDeviceChangeAvailable - Resolves with true if the device change is available and with false if not.

// The accepted deviceType values are - 'output', 'input' or undefined.
api.isDeviceChangeAvailable(deviceType).then(isDeviceChangeAvailable => {
    ...
});

• isDeviceListAvailable - Resolves with true if the device list is available and with false if not.

api.isDeviceListAvailable().then(isDeviceListAvailable => {
    ...
});

• isMultipleAudioInputSupported - Resolves with true if multiple audio input is supported and with false if not.

api.isMultipleAudioInputSupported().then(isMultipleAudioInputSupported => {
    ...
});

• setAudioInputDevice - Sets the audio input device to the one with the label or id that is passed.

api.setAudioInputDevice(deviceLabel, deviceId);

• setAudioOutputDevice - Sets the audio output device to the one with the label or id that is passed.

api.setAudioOutputDevice(deviceLabel, deviceId);

• setVideoInputDevice - Sets the video input device to the one with the label or id that is passed.

api.setVideoInputDevice(deviceLabel, deviceId);

You can control the embedded Jitsi Meet conference using the JitsiMeetExternalAPI object by using executeCommand:

api.executeCommand(command, ...arguments);

The command parameter is String object with the name of the command. The following commands are currently supported:

• displayName - Sets the display name of the local participant. This command requires one argument - the new display name to be set.

api.executeCommand('displayName', 'New Nickname');

• password - Sets the password for the room. This command requires one argument - the password name to be set.

api.executeCommand('password', 'The Password');

• sendTones - Play touch tones.

api.executeCommand('sendTones', {
    tones: string, // The dial pad touch tones to play. For example, '12345#'.
    duration: number, // Optional. The number of milliseconds each tone should play. The default is 200.
    pause: number // Optional. The number of milliseconds between each tone. The default is 200.
});

• subject - Sets the subject of the conference. This command requires one argument - the new subject to be set.

api.executeCommand('subject', 'New Conference Subject');

• toggleAudio - Mutes / unmutes the audio for the local participant. No arguments are required.

api.executeCommand('toggleAudio');

• toggleVideo - Mutes / unmutes the video for the local participant. No arguments are required.

api.executeCommand('toggleVideo');

• toggleFilmStrip - Hides / shows the filmstrip. No arguments are required.

api.executeCommand('toggleFilmStrip');

• toggleChat - Hides / shows the chat. No arguments are required.

api.executeCommand('toggleChat');

• toggleShareScreen - Starts / stops screen sharing. No arguments are required.

api.executeCommand('toggleShareScreen');

• toggleTileView - Enter / exit tile view layout mode. No arguments are required.

api.executeCommand('toggleTileView');

• hangup - Hangups the call. No arguments are required.

api.executeCommand('hangup');

• email - Changes the local email address. This command requires one argument - the new email address to be set.

api.executeCommand('email', 'example@example.com');

• avatarUrl - Changes the local avatar URL. This command requires one argument - the new avatar URL to be set.

api.executeCommand('avatarUrl', 'https://avatars0.githubusercontent.com/u/3671647');

• sendEndpointTextMessage - Sends a text message to another participant through the datachannels.

api.executeCommand('receiverParticipantId', 'text');

You can also execute multiple commands using the executeCommands method:

api.executeCommands(commands);

The commands parameter is an object with the names of the commands as keys and the arguments for the commands as values:

api.executeCommands({
    displayName: [ 'nickname' ],
    toggleAudio: []
});

You can add event listeners to the embedded Jitsi Meet using the addEventListener method. NOTE: This method still exists but it is deprecated. JitsiMeetExternalAPI class extends EventEmitter. Use EventEmitter methods (addListener or on).

api.addEventListener(event, listener);

The event parameter is a String object with the name of the event. The listener parameter is a Function object with one argument that will be notified when the event occurs with data related to the event.

The following events are currently supported:

• cameraError - event notifications about Jitsi-Meet having failed to access the camera. The listener will receive an object with the following structure:

{
    type: string, // A constant representing the overall type of the error.
    message: string // Additional information about the error.
}

• avatarChanged - event notifications about avatar changes. The listener will receive an object with the following structure:

{
    id: string, // the id of the participant that changed his avatar.
    avatarURL: string // the new avatar URL.
}

• audioAvailabilityChanged - event notifications about audio availability status changes. The listener will receive an object with the following structure:

{
    available: boolean // new available status - boolean
}

• audioMuteStatusChanged - event notifications about audio mute status changes. The listener will receive an object with the following structure:

{
    muted: boolean // new muted status - boolean
}

• endpointTextMessageReceived - event notifications about a text message received through datachannels. The listener will receive an object with the following structure:

{
    senderInfo: {
        jid: string, // the jid of the sender
        id: string // the participant id of the sender
    },
    eventData: {
        name: string // the name of the datachannel event: `endpoint-text-message`
        text: string // the received text from the sender
    }
}

• micError - event notifications about Jitsi-Meet having failed to access the mic. The listener will receive an object with the following structure:

{
    type: string, // A constant representing the overall type of the error.
    message: string // Additional information about the error.
}

• screenSharingStatusChanged - receives event notifications about turning on/off the local user screen sharing. The listener will receive object with the following structure:

{
    on: boolean, //whether screen sharing is on
    details: {

        // From where the screen sharing is capturing, if known. Values which are
        // passed include 'window', 'screen', 'proxy', 'device'. The value undefined
        // will be passed if the source type is unknown or screen share is off.
        sourceType: string|undefined
    }
}

• dominantSpeakerChanged - receives event notifications about change in the dominant speaker. The listener will receive object with the following structure:

{
    id: string //participantId of the new dominant speaker
}

• tileViewChanged - event notifications about tile view layout mode being entered or exited. The listener will receive object with the following structure:

{
    enabled: boolean, // whether tile view is not displayed or not
}

• incomingMessage - Event notifications about incoming messages. The listener will receive an object with the following structure:

{
    from: string, // The id of the user that sent the message
    nick: string, // the nickname of the user that sent the message
    message: string // the text of the message
}

• outgoingMessage - Event notifications about outgoing messages. The listener will receive an object with the following structure:

{
    message: string // the text of the message
}

• displayNameChange - event notifications about display name changes. The listener will receive an object with the following structure:

{
    id: string, // the id of the participant that changed his display name
    displayname: string // the new display name
}

• deviceListChanged - event notifications about device list changes. The listener will receive an object with the following structure:

{
    devices: Object // the new list of available devices.
}

NOTE: The devices object has the same format as the getAvailableDevices result format.

• emailChange - event notifications about email changes. The listener will receive an object with the following structure:

{
    id: string, // the id of the participant that changed his email
    email: string // the new email
}

• feedbackSubmitted - event notifications about conference feedback submission

{
    error: string // The error which occurred during submission, if any.
}

• filmstripDisplayChanged - event notifications about the visibility of the filmstrip being updated.

{
    visible: boolean // Whether or not the filmstrip is displayed or hidden.
}

• participantJoined - event notifications about new participants who join the room. The listener will receive an object with the following structure:

{
    id: string, // the id of the participant
    displayName: string // the display name of the participant
}

• participantKickedOut - event notifications about a participants being removed from the room. The listener will receive an object with the following structure:

{
    kicked: {
        id: string, // the id of the participant removed from the room
        local: boolean // whether or not the participant is the local particiapnt
    },
    kicker: {
        id: string // the id of the participant who kicked out the other participant
    }
}

• participantLeft - event notifications about participants that leave the room. The listener will receive an object with the following structure:

{
    id: string // the id of the participant
}

• passwordRequired - event notifications fired when failing to join a room because it has a password.

• videoConferenceJoined - event notifications fired when the local user has joined the video conference. The listener will receive an object with the following structure:

{
    roomName: string, // the room name of the conference
    id: string, // the id of the local participant
    displayName: string, // the display name of the local participant
    avatarURL: string // the avatar URL of the local participant
}

• videoConferenceLeft - event notifications fired when the local user has left the video conference. The listener will receive an object with the following structure:

{
    roomName: string // the room name of the conference
}

• videoAvailabilityChanged - event notifications about video availability status changes. The listener will receive an object with the following structure:

{
    available: boolean // new available status - boolean
}

• videoMuteStatusChanged - event notifications about video mute status changes. The listener will receive an object with the following structure:

{
    muted: boolean // new muted status - boolean
}

• readyToClose - event notification fired when Jitsi Meet is ready to be closed (hangup operations are completed).

• subjectChange - event notifications about subject of conference changes. The listener will receive an object with the following structure:

{
    subject: string // the new subject
}

• suspendDetected - event notifications about detecting suspend event in host computer.

You can also add multiple event listeners by using addEventListeners. This method requires one argument of type Object. The object argument must have the names of the events as keys and the listeners of the events as values. NOTE: This method still exists but it is deprecated. JitsiMeetExternalAPI class extends EventEmitter. Use EventEmitter methods.

function incomingMessageListener(object)
{
// ...
}

function outgoingMessageListener(object)
{
// ...
}

api.addEventListeners({
    incomingMessage: incomingMessageListener,
    outgoingMessage: outgoingMessageListener
});

If you want to remove a listener you can use removeEventListener method with argument the name of the event. NOTE: This method still exists but it is deprecated. JitsiMeetExternalAPI class extends EventEmitter. Use EventEmitter methods( removeListener).

api.removeEventListener('incomingMessage');

If you want to remove more than one event you can use removeEventListeners method with an Array with the names of the events as an argument. NOTE: This method still exists but it is deprecated. JitsiMeetExternalAPI class extends EventEmitter. Use EventEmitter methods.

api.removeEventListeners([ 'incomingMessage', 'outgoingMessageListener' ]);

You can get the number of participants in the conference with the following API function:

const numberOfParticipants = api.getNumberOfParticipants();

You can get the avatar URL of a participant in the conference with the following API function:

const avatarURL = api.getAvatarURL(participantId);

You can get the display name of a participant in the conference with the following API function:

const displayName = api.getDisplayName(participantId);

You can get the email of a participant in the conference with the following API function:

const email = api.getEmail(participantId);

You can get the iframe HTML element where Jitsi Meet is loaded with the following API function:

const iframe = api.getIFrame();

You can check whether the audio is muted with the following API function:

api.isAudioMuted().then(muted => {
    ...
});

You can check whether the video is muted with the following API function:

api.isVideoMuted().then(muted => {
    ...
});

You can check whether the audio is available with the following API function:

api.isAudioAvailable().then(available => {
    ...
});

You can check whether the video is available with the following API function:

api.isVideoAvailable().then(available => {
    ...
});

You can invite new participants to the call with the following API function:

api.invite([ {...}, {...}, {...} ]).then(() => {
    // success
}).catch(() => {
    // failure
});

NOTE: The format of the invitees in the array depends on the invite service used for the deployment.

You can remove the embedded Jitsi Meet Conference with the following API function:

api.dispose();

NOTE: It's a good practice to remove the conference before the page is unloaded.