Skip to main content
Freedeck uses Socket.IO for real-time communication between the desktop companion app and mobile clients. The API supports authentication, tile management, plugin control, and RPC operations.

Connection & Authentication

Initial Connection

When connecting to Freedeck, clients must follow this handshake process:

Authentication Flow

If authentication is enabled, you must authenticate before accessing protected features:

Event Reference

Core Events

Default Events

These events control core Freedeck functionality:

Companion Events

These events are used by the desktop companion app for tile and profile management:

RPC Events

Remote Procedure Call events for advanced integrations:

FDWS Events

Freedeck WebSocket events for launcher integration:

Relay Events

Events for relay server functionality:

Data Structures

Server Information

Plugin Information

Error Handling

Best Practices

Authentication: Always validate your temp login ID before sending credentials. It’s required by the server.
Rate Limiting: Be mindful of rapid tile operations, the server has abuse protection.
Compression: Server responses are gzip compressed for efficiency.
Security: Never hardcode passwords in client applications. Use secure credential storage.

Examples

Basic Mobile Client

Companion App Integration