Documentation

SealBind issues software licenses, binds activations to devices, and lets your application verify a license offline using a signed Ed25519 token. This is the developer integration guide.

How it fits together

Each SealBind account owns an Ed25519 keypair. The private key signs license tokens on our side; the public key is served openly so your app can verify tokens without contacting us. You issue a license per customer, ship the signed token with your software, and verify it at runtime.

• Offline verification — check authenticity and expiry with only the account public key. No network call, no dependency on SealBind uptime on your hot path.
• Online validation — call the API when you want the authoritative answer, including revocation and device-count checks.

Base URL

All endpoints are served from the SealBind app under a versioned path:

https://sealbind.io/api/v1

Next steps

Use the Vendor API reference to create products and issue, activate, validate, or revoke licences. Then read Offline verification for the signed token format and verification examples.