License API
Get Product Versions
6min
Returns metadata on all the available versions of a product
GET
Request
Query Parameters
hardware_id
required
String
Unique hardware ID generated for the client device
product
required
String
Product short code
license_key
optional
String
Required if product is key-based (see section below)
username
optional
String
Required if product is user based (see section below)
license_id
optional
Number
Ensures that the action affects only the license with the specified ID. This is useful if e.g. you have multiple licenses for the same product assigned to the same user. For obtaining a list of licenses assigned to a user, see "User Licenses"
env
optional
String
Environment identifier, e.g. "win", "win32", "win64", "mac", "linux", "linux32", "linux64"
channel
optional
String
Channel identifier, e.g. "staging", "prod"
Header Parameters
Date
required
String
In RFC7231 format (see "License API Authorization"), eg.: Thu, 17 Nov 2022 20:51:35 GMT
Authorization
required
String
See "License API Authorization" article

Product versions are returned up to the existing maintenance_period or validity_period on the license. If those fields are not defined on a license, all versions will be returned by default.


There are two types of product licenses based on how the client application authorizes itself to interact with a license:
- Key-based product licenses: client interactions with the license have to be authorized using a license_key
- User-based product licenses: the license has a corresponding "license user" instead of a license key. Client interactions with the license have to be authorized using a username
If an error occurs, the response will have an HTTP status code of 400 or higher, and the response body will contain an error description in the following format:


Updated 17 Jan 2025
Did this page help you?