C# licensing API

Validate a licence key

One POST to /apps/{appId}/licenses/authenticate. .NET 6+. No packages beyond the BCL.

using System.Net.Http.Json;

var http = new HttpClient { BaseAddress = new Uri("https://api.evora.lol/api/developer-api/") };
http.DefaultRequestHeaders.Authorization =
    new("Bearer", Environment.GetEnvironmentVariable("EVORA_API_KEY"));

var appId = Environment.GetEnvironmentVariable("EVORA_APP_ID");

var res = await http.PostAsJsonAsync(
    $"apps/{appId}/licenses/authenticate",
    new { licenseKey });

res.EnsureSuccessStatusCode();
var data = await res.Content.ReadFromJsonAsync<AuthResult>();

record AuthResult(bool Authenticated, Subscription? Subscription);
record Subscription(int Level, string? Name, DateTime? ExpiresAt, bool Active);

What you get back

• authenticated — whether the key is valid and usable right now.
• subscription.level and subscription.name — the tier you configured.
• subscription.active — false when expired or paused. Use this, not the raw expiry.
• subscription.hwid — the bound device, when HWID locking is on.

Keep the key server-side

The API key is a server credential. The safe shape is always: browser → your server → Evorion. Your backend holds the key, validates the licence, then issues your own session.

• Never ship ag_sk_ keys to a client of any kind.
• Scope each key to the minimum it needs, and to one application where you can.
• Rotate from the dashboard; keys are shown once on creation.

Native apps want the C++ SDK

If you are shipping a Windows binary to end users, REST alone leaves the client unprotected. The C++ SDK adds encrypted bodies, device-bound credentials and runtime protection that a dashboard toggle can change mid-session.

• SDK documentation
• Full REST reference