Release Notes

Cortex 2.4.0 - Mars 2020

Cortex 2.3.0 - December 2019

  • New parameter includeFlexMappings added to the method queryHeadsets

  • New field lastLoginTime added in the result of the method getUserLogin

Cortex 2.2.1- October 2019

  • New method added configOptOut

  • New parameter connectionType added to the method controlDevice

  • New parameter experimentId added to the method createRecord

  • New Warning added when the available space on the hard drive is too low

  • New Warning added when the opt-out configuration changes

  • New label isActive in the performance metrics sample object

Cortex 2.2.0 - September 2019

This version didn't introduce any change in the API.

Cortex 2.1.1 - August 2019

Cortex 2.1.0 - August 2019

  • New methods added to manage the Subjects

Changes from Cortex 1.x to Cortex V2.0

There are significant changes from Cortex API version 1.x to 2.0.

WebSocket URL

To connect to Cortex 1.x, you used the url wss:// In Cortex 2.0, you must use wss://localhost:6868

See Connecting to the Cortex API for details.


In Cortex 2.0, the user must login with EmotivID through the EMOTIV App. So, the API doesn't have a login or logout method anymore.

Third party applications must be approved by the user before using the Cortex API. See the new method requestAccess.

The method authorize doesn't accept "anonymous mode" anymore. You must provide a client id and client secret.

See Authentication for details.


Call the method controlDevice to connect a headset to Cortex. If the headset is not connected, then you can't create a session with this headset.

See Headsets for details.


Some methods have been removed or renamed.

Method name in v1

Equivalent in v2

login, logout

See getUserLogin


The user must accept the EULA in EMOTIV App. You can call getUserInformation to check if the user already accepted the EULA or not


See controlDevice


See updateRecord

The parameters and result format of some methods have changed. If you get an error when calling a method, please check its documentation.