This docs hub gives you copy-ready SDK examples for the languages your users actually use.
Each snippet is paired with the features it unlocks, so you can wire licensing, support, variables,
webhooks, and plan-aware flows without guessing.
The active snippet updates when you choose a language. Use it as a starter, then customize your app flow, UI, or CLI around it.
WinForms / .NET desktopLicense-first flowPlan-aware support
Best for C# starter integrations and plan-aware feature unlocks.
StarterWinForms / .NET desktop
var client = new AuthSP(
name: "YOUR_APP_NAME",
ownerid: "YOUR_OWNER_ID",
version: "1.0"
);
if (client.license(licenseKeyTextBox.Text.Trim()).success)
{
// Unlock the app, load user variables, and continue to the main screen.
}
Feature guide
Use AuthSP features the same way in every language
Initialize, validate, read variables, trigger webhooks, and branch by plan once the user is authenticated.
License verification
All SDKs should verify the license early, then switch to your authenticated app state.
HWID protection
Bind the license to the machine fingerprint so reuse and sharing become harder.
User variables
Fetch custom variables for per-user configuration, feature flags, or runtime settings.
Webhook flows
Use webhooks to keep billing, support, logs, and external automation in sync.
Support workflows
Route bugs, feedback, and product questions into support so the project stays up to date.
Plan-aware features
Use the plan level to show the right controls, routes, and entitlement checks.
Best practices
Keep your AuthSP apps fast and maintainable
Use a consistent SDK wrapper, keep your API endpoint stable, and move UI text or feature flags into variables when possible.
Stable API endpoint
Keep the same base URL in production and handle failover only when necessary.
Secure secrets
Never ship private secrets in the client if you can validate them safely on the server.
Plan-aware UI
Show controls and features based on the account plan to reduce confusion and support tickets.
AuthSP