Official SDKs
Use the language reference for current package names and installation requirements. The published SDK 2.1.1 release covers all eight clients; platform limits still apply, including separate Unity target checks.
SDK 2.1.1 offline migration: configure trusted tenant public keys independently of cache files. No pins means no cached authorization. Persisted offline helpers use the configured client and re-verify the original signed token on every read. Offline setup and migration.
SDK Overview
The SDK 2.1.1 application and Store tutorials show current installation commands and application fragments. Supply inputs and UI/host control flow from your app. Online validation alone does not enable offline grace, register a device or reserve a floating session. Configure trusted public keys for offline use; C++ installation needs its documented vcpkg registry and pinned baseline.
SDK 2.1.1 request settings
A slow or unavailable license server must not leave your application waiting indefinitely. All eight SDKs default to a 10-second timeout for each attempt and two additional attempts for safe requests. The usual backoff is 250 milliseconds, then 500 milliseconds. This is not a single 10-second deadline for the complete operation: activation also fetches a nonce.
- License validation, nonce/public-key retrieval and floating heartbeat may retry a network failure or HTTP 5xx response. Set the retry count to zero to disable these retries; the range is 0–5.
- Floating checkout, activation POST, usage reporting, device removal and checkin are sent once. A lost response can follow a successful server change, so retrying these blindly can duplicate work.
- HTTP 3xx/4xx responses and malformed successful responses do not retry. SDK-owned transports do not follow redirects, so configure the final HTTPS API address directly.
For validate/activate, branch on the server's error code when available. Otherwise
HttpError means an HTTP rejection, InvalidResponse means malformed
successful license/nonce evidence and RequestFailed means the network/5xx attempts
were exhausted without a usable signed cache. Rejection or malformed successful evidence never
becomes cached authorization. A network outage can use only a separately trusted, unexpired proof.
| SDK | Configuration |
|---|---|
| .NET | PermitCoreOptions.Timeout = TimeSpan.FromSeconds(10) and MaxRetries = 2 |
| Node.js | Use the options-object constructor with timeoutMs: 10000, maxRetries: 2. |
| Python | PermitCoreClient(url, timeout=10, max_retries=2) |
| Java | The extended constructor takes trusted keys, cache path, device ID, Duration.ofSeconds(10), then 2. |
| C++ | The constructor takes URL, 10 timeout seconds, cache toggle, trusted keys, cache path, device ID, then 2 retries. |
| PHP | The constructor takes URL, cache toggle, 10 timeout seconds, trusted keys, cache path, device ID, then 2 retries. |
| Go | Options.Timeout uses time.Duration. MaxRetries is an optional integer pointer: nil defaults to two; a pointer to zero disables retries. |
| Unity | Named constructor arguments timeoutSeconds: 10, maxRetries: 2; custom transports must honor the supplied timeout and preserve any received status. |
Timeout mechanisms follow each runtime: Python uses socket I/O timeouts; Unity delegates to its transport. Caller cancellation is separate from retry policy. Unity's default adapter disables redirects; WebGL needs Unity 2021.3 or later for that protection and fails closed on older versions. Portable .NET tests do not certify an Editor, IL2CPP or browser build. Verify your actual target before shipping.
Install SDK 2.1.1 using the SDK installation references and follow the offline migration guide when upgrading from 1.x.
PermitCore provides official SDK packages for .NET, Node.js, Python, Java, C++, PHP, Go, and Unity. Each SDK wraps the public REST API with idiomatic language bindings, automatic HWID fingerprinting and signed offline grace period caching. Floating checkout, heartbeat and checkin are available in all eight clients in SDK 2.1.1. Earlier Java/C++ releases use the REST endpoints for floating sessions.
SDK 2.1.1: All eight SDKs share the operations below. Its validate/activate calls treat HTTP rejections as authoritative: a 4xx response cannot become successful offline validation. Network/5xx outages can still use a verified signed cache within its deadline. Use version 2.1.1 for these examples and follow the offline migration guide when upgrading from 1.x.
In SDK 2.1.1, floating checkout/heartbeat failures return success=false with no token or expiry: RequestFailed for network/HTTP/invalid responses, or the server denial code with FloatingDenied as the default. Floating requests never use offline cache. TryCheckin (idiomatic spelling varies by language) confirms only HTTP 204; legacy checkin is best effort and relies on server expiry if release is unconfirmed. Only heartbeat uses safe bounded network/5xx retries; checkout and checkin are sent once.
SDK 2.1.1 provides device removal in every client: supply tenant slug, license key and activation ID. Only HTTP 204 confirms removal. OTP/account Portal protection still requires the customer Portal flow. Each client attempts to discard that key's grace cache; separately issued offline tokens retain their signed bounds. Usage reporting accepts an integer quantity (default 1; values below 1 normalize to 1) and optional nested metadata object. Only JSON recorded: true confirms recording. Neither operation uses offline fallback or automatic retries. A false result after a lost response does not prove no server-side change occurred.
Current capability matrix
All eight clients support validate, activate, product binding, feature checks, offline token verification and signed grace caches. The table records the capabilities of SDK 2.1.1. Device removal and boolean usage reporting now have wrappers in all eight. Shared transport defaults, safe retries and core license error handling are covered below; broader optional DTO edges remain runtime-specific.
| SDK | Floating seats | Meter reporting | Device deactivation |
|---|---|---|---|
| .NET | SDK | SDK | SDK |
| Node.js | SDK | SDK | SDK |
| Python | SDK | SDK | SDK |
| Java | SDK | SDK | SDK |
| C++ | SDK | SDK | SDK |
| PHP | SDK | SDK | SDK |
| Go | SDK | SDK | SDK |
| Unity | SDK | SDK | SDK |
SDK means the operation has a wrapper in version 2.1.1. Java/C++ retain legacy detailed meter results and add canonical boolean tryMeter/try_meter calls; other clients use MeterAsync/meter/Meter. All eight use 10-second defaults and two safe retries; follow the configuration guide for idiomatic options. Source ZIPs include test fixtures. .NET source/tests require the .NET 10 SDK even when your application targets .NET 6–9. Unity portable-core tests do not certify Editor or IL2CPP builds.
PermitCore.Client — NuGet · .NET 6–10, zero dependenciespermitcore — npm · TypeScript-first, native fetchpermitcore — pip · Python 3.8+, standard library online; cryptography for offline verificationMaven · Java 11+, built-in
HttpClientCMake 3.14+ · C++17, libcurl, OpenSSL; nlohmann/json 3.11.3+
Composer · PHP 8.0+, ext-curl, ext-json, and ext-openssl for offline verification
Go 1.21+ · standard library only, crypto/ecdsa for offline verification
Unity 2021.2+ · zero dependencies, Desktop/Mobile/Console/WebGL