Solutions

Software Licensing API for Developers

A software licensing API lets your app check a customer's license and register the device. PermitCore provides POST /api/v1/validate and POST /api/v1/activate with eight official SDKs. Start with the Free plan and keep administrator secrets out of the distributed app.

The problem with building this yourself

Every software vendor eventually needs to answer "is this a real, currently-valid license key." Rolling that yourself means a database schema, a hashing scheme that doesn't leak plaintext keys if the DB is stolen, race-condition-safe activation counting, rate limiting so the endpoint can't be brute-forced, and — if you ever sell direct — a checkout flow. Most of that is undifferentiated work that has nothing to do with the software you're actually trying to sell.


How it works

Default Admin creation encrypts keys in the browser with your passphrase. Validation and activation receive plaintext over HTTPS and compute a server-keyed lookup value. Store delivery and optional escrow use server-managed protection; privileged operational access is a separate boundary. See the encryption reference.

curl -X POST https://your-domain.com/api/v1/validate \
  -H "Content-Type: application/json" \
  -d '{"licenseKey":"PERMIT-A3K7-MN2P-QR9X-TZ5W","expectedProductId":"7f3e9a2b-1c4d-4e8f-9a6b-3d2c1e0f5a8b"}'

# Response
{ "isValid": true, "productName": "Acme Video Editor Pro", "productId": "7f3e9a2b-1c4d-4e8f-9a6b-3d2c1e0f5a8b", "expiresAt": null }

Activation works the same shape, plus a nonce (GET /nonce first) and it atomically increments the license's activation counter — PostgreSQL row-level locking means two simultaneous activation calls for a seat-limited key can't both win the last seat. See the full API reference for every endpoint, error code, and language example.


What you get beyond the two endpoints

8 official SDKs
.NET, Node.js, Python, Java, C++, PHP, Go, and Unity — each wraps the two endpoints with retry logic, timeout handling, and idiomatic error types, so you're not hand-rolling HTTP calls.
Offline & grace-period support
Signed offline activation tokens for air-gapped machines, plus an SDK-side cached grace period so a brief network outage doesn't lock out a legitimate customer.
Built-in abuse protection
Per-IP and per-tenant rate limiting, plus anomaly detection that catches a single valid key being shared across many distinct IPs — not just brute-force guessing.
Feature flags per license
Store a JSON feature map on each license and read which modules are enabled at validation time — upsell without shipping new keys.

Start validating license keys today

Free tier available. No credit card required.

Frequently asked questions

What does a software licensing API do?

It checks whether a license grants access to a product and can register the installation against the license's activation limits.

Do I need an administrator API key in my app?

No. The public validate and activate endpoints use the customer license key. Activation also requires a nonce.

Can I validate a license offline?

PermitCore supports signed offline proof. Your application must verify the trusted signing key and enforce the proof's expiry and product scope.