TeamSpeak 5.0.0-beta54.x – Announcements – TeamSpeak

Hello everyone!

Beta version 54 is now available to test! This week we fixed some bugs that were reported by the TS community and added a few new things for everyone to try out.

Hopefully the changelog and extra notes should explain the update well enough.

Full changelog


Beta 54.1

  • Fixed possible crash when remote apps setting is active

Beta 54

  • Fixed server links not behaving correctly with some input
  • Fixed connecting indefinitely when using a privilege key on connect
  • Fixed bans not being created / no error being shown when user left server
  • Fixed whisper notifications appearing on every server rather than the server on which they happened


  • Added sound when receiving a whisper
  • Added context menu to user name on join, leave, kick and ban messages
  • Added notification center to the bell icon
  • Added ability for third party applications to be notified of TeamSpeak events
  • Changed default view to chat when selecting a channel

Remote application information

Information received by remote apps contain information regarding clients. These are currently numbers represented as a string, which correspond to the ClientProperties Enum.
The plan is to change this and make those keys descriptive strings rather than β€œ10” for example.

Third party applications need to establish a connection and then send an authentication request as follows:

    type: 'auth';
    payload: {
        identifier: string; // com.myself.myapp
        version: string; // SemVer
        name: string; // Display name for UI
        description: string;
        content: {apiKey: string;};

The user will then need to authorize the remote application in the settings before the application can receive any events.
Once the user has authorized the application, said application will start receiving events through its connection.

The remote application will receive the following response once it has been authorized. For future connections the application will need to send the authorization request with the apiKey set to the one received in the reply to the latest authorization request.

Authorization reply:

    type: 'auth';
    payload: {
        apiKey: string;

Notes for this thread

  • Feedback as per always is welcome in this thread :smiley: . Issues that are not related to this update belong to it’s own thread.
  • We suggest to place your wishes for upcoming releases in existing or new threads in the suggestion area instead of the release thread. We mention this because each update post will be closed after some days and the wish or suggestion could be lost.
  • We allow ourselves to delete all the off-topic posts from this thread.

Leave a Reply

Your email address will not be published. Required fields are marked *