Concepts overview

Blazeauth separates dashboard configuration (apps, environments, licenses, variables) from runtime access (WebSocket sessions).

Application

An application is your product. All runtime operations happen within a single application context.

Environment and API key

An environment is a configuration slice of an application (for example: development, staging, production). Each environment provides a socket API key used by initialize.

Session

A session is a WebSocket connection plus server-side session state. Initialization and authorization are stored inside the session, so you can make multiple API calls without re-sending credentials each time.

Account

An account is a credentials-based user entry inside the application (login/password or email/password). Accounts can require an active license depending on the application settings.

License

A license is a license key that can be validated in real time. You can:

• Authorize directly by license (auth_by_license), or
• Link a license to a credentials account (link_license_to_account)

Licenses return levels and can have expiration (time_left).

Levels

levels is a list of strings (for example: ["admin", "pro"]). It is returned by authorization endpoints and can be used to gate features in your client.

Variables

A variable is a server-controlled value (name → content string) you can fetch at runtime with get_variable.

Protected files

Protected files are stored server-side and transferred in chunks over the same WebSocket session using get_file_metadata and transfer_file.