User Data
After a successful login or registration, the SDK keeps the current identity data available on its client object. Read it wherever your app needs to show the signed-in person’s details. It is cleared when the person signs out or AuthlyX confirms that access has ended. The exact access syntax differs by language, as shown below.
The exact object shape depends on the language. The API fields use camelCase. C# exposes a typed UserData object with PascalCase properties. C++, Python, JavaScript, TypeScript, and Go keep the API fields and add a smaller set of PascalCase aliases. Java and Rust expose the API fields directly.
Fields you can read
The C++, Python, JavaScript, TypeScript, and Go SDKs currently add these PascalCase aliases: Username, LicenseKey, SID, Email, Plan, ExpiryDate, Country, IpAddress, and DeviceLimit. Their raw API fields, including features, featureValues, metadata, registeredAt, and lastLogin, remain camelCase. Java and Rust use the raw API names. C# exposes the typed properties shown in the table, plus Hwid as an alias for SID and Subscription as an alias for Plan.
Some fields do not apply to every sign-in. For example, a device identity may not have a username, email, or license key. Do not assume an empty field means the login failed.
Example data
This is an example of the identity information returned after a successful sign-in. The values are illustrative; your app receives its own account data.
Read values in your app
The SDK stores this data after login. These examples read it; they do not make another API request.
C#
JavaScript / Node.js
TypeScript
Python
C++
Java
Go
Rust
Use Check session when you need current authorization. User Data is convenient account information; it is not a substitute for a session check or a server-side permission check.

