Skip to main content
The Devolens (formerly Cryptolens) Web API is the HTTPS interface that applications, backend services, and third-party systems use to work with licensing data. It is used for license verification, key creation, activation management, customer access, usage data, and automation. For most client applications, we recommend using one of the client SDKs. The SDKs call the Web API for you and include helpers for common licensing tasks. You can also call the Web API directly when you need a custom backend integration, an unsupported programming language, or a workflow that is not covered by an SDK.

​
How it fits

At a high level, the Web API is the integration layer between your systems and Devolens:
This makes the Web API useful both for simple license checks inside an application and for larger SME or enterprise workflows where licensing is connected to sales, billing, customer administration, support, or internal tools.

​
Common use cases

You can use the Web API to:
  • Activate and verify license keys.
  • Create, extend, block, or update license keys from your backend.
  • Assign license keys to customers and retrieve licenses linked to a customer.
  • Manage activated machines, user seats, floating seats, or other activation identifiers.
  • Store and update license metadata, such as feature configuration or usage counters.
  • Integrate Devolens with payment providers, CRM systems, provisioning workflows, or internal admin portals.
  • Support platforms where no official client SDK is available.

​
SDKs vs direct API calls

​
Security basics

Access to the Web API is controlled with access tokens. Create separate access tokens for different workflows and give each access token only the permissions it needs.
See Access tokens and RSA public key for setup examples and the available permissions and lock settings. One access token can have both the Activate and Deactivate permissions.
For example, an access token used by a backend payment workflow may need permission to create or update license keys. An access token distributed inside a desktop or mobile application should be much more limited. Do not place admin or key-generation access tokens in client-side applications. For license verification, use signed responses where supported and verify the response with your RSA public key. Your application should also check the license properties that matter for your product, such as product ID, expiry date, blocked status, features, and machine-binding or activation rules.

​
Direct request example

If you are using an unsupported language or building a custom integration, you can call the Web API directly. For example, this request retrieves information about a license key:
The exact parameters depend on the method you call. See the Web API reference for endpoint-specific request and response details.

​
Enterprise deployment options

Most applications can call Devolens directly through the client SDKs or the Web API. Some enterprise customers have additional network or compliance requirements. In those cases, you can also use:
  • Reverse proxy, if requests need to go through your own domain or IP address.
  • License server, if customer machines have limited internet access or need a local licensing gateway.
  • Backend-only API calls, if license provisioning, billing, or customer administration should be isolated from client applications.

​
Next steps