Web Loader

Web login allows users to authenticate into your desktop application directly from your website or our customer panel using a temporary token.

Unlike standard API login endpoints, this method works by sending credentials to a local HTTP listener running inside your application.

Endpoint (Local)

GET http://localhost:1337/handshake/?user={username}&token={token}

How It Works

Your application starts the web login listener:

The application listens on:
https://localhost:1337/handshake

Your website/customer panel redirects the user to:
https://localhost:1337/handshake/?user={username}&token={token}

The client (c# in this example):

Receives the request

Extracts user and token

Sends a login request to KeyAuth servers

If successful:

The user is logged into the application

User data is loaded

Request Parameters

Parameter	Required	Description
user	Yes	Username of the account
token	Yes	Temp web login token

Internal Request Sent to KeyAuth

After receiving the web request, the client sends the normal params as a regular login request, but now with the `token` param.

Requirements

Application must already be initialized

Application must be running before web login is triggered

Port 1337 must be available

Browser must allow requests to localhost

Security Notes

Tokens must be temporary and single-use

Never expose permanent credentials in the browser

Always validate tokens server-side before issuing them

Only allow trusted websites to trigger web login

Bind only to localhost (never public interfaces)

Common Issues

App not responding

Ensure your application is running and listening on:
http://localhost:1337/handshake/

Button does nothing

Port already in use

Notes

Designed for website -> desktop authentication

Not a replacement for API-based login endpoints

Ideal for one-click login buttons, dashboards, and download portals

Web Buttons

Web buttons allow owners to add custom buttons to the customer panel that can trigger actions inside the desktop application.

After the user logs in with web_login(), your application can wait for a specific button event using:

For example, an owner could add a button named close to the customer panel. When the customer clicks that button on the website, the desktop application detects it and can run custom login.

Common Button Uses

Web Buttons can be used for actions such as:

Closing the program

Starting a download

Opening a menu

Refreshing user data

Unlocking a feature

Triggering a custom in-app event

Important Notes

web_login() should be called before waiting for button events

The button name must match the customer panel button name exactly

Button events are intended for website-to-application communication

Your application decides what happens after the button is clicked

Endpoint (Local)#

How It Works#

Request Parameters#

Internal Request Sent to KeyAuth#

After receiving the web request, the client sends the normal params as a regular login request, but now with the token param.#

Requirements#

Security Notes#

Common Issues#

Notes#

Web Buttons#

Common Button Uses#

Important Notes#