Skip to main content
The Devolens (formerly Cryptolens) API can be called from your application or from other services (e.g. CRM or payment provider). To get you up and running quickly, we will focus on how to verify a license inside your application. If you have not created any products or licenses yet, we recommend following the Getting Started Guide. Open Getting Started Guide Once you have created a product, you can refer to the Quick Start section for detailed code examples tailored to the product.

​
Verify a License Key

The request below calls Activate. After completing the guide, replace the placeholders with your own values.
MachineCode applies when Maximum Number of Machines > 0. Omit it when machine locking is disabled. For production use, verify the signed response and the license fields your application relies on. Consider a cached signed-license fallback for temporary connection failures.

​
SDKs and API Reference

Use a client SDK for application integration. For direct HTTP calls, see the Web API guide. Endpoint details are in the Web API 3 reference.

​
Credentials

These values belong to your account. Use a separate, limited-scope access token for each workflow. Never include administrative or key-generation permissions in a client application. See the authentication guide.

​
RSA Public Key

Use this public key to verify signed license responses from Devolens. [PublicKey]

​
Access Token

This pre-generated token includes access to the Activate and GetKey methods. You can create a separate limited-scope token on the Access Token page. [token]