License heartbeat
The Heartbeat endpoint is used to determine whether a specific device is still active. You should call this endpoint at regular intervals (e.g., once every 30 minutes). This process also validates the license key in a similar way to the Verify License endpoint.
Path Parameters
Your team's UUID. You can find this value in your team's settings on the Lukittu dashboard. Format: UUID v4.
Body
A unique identifier for the client device. Typically a hardware ID or another identifier that remains consistent across sessions. Device identifier must not contain spaces and must be between 10 and 1000 characters.
10 - 1000The Lukittu license key. Lukittu license keys always follow this format: XXXXX-XXXXX-XXXXX-XXXXX-XXXXX where X is an uppercase letter (A-Z) or a digit (1-9).
A client-generated random string used to prevent request interception. The Lukittu backend signs this challenge with its RSA private key. You can then validate the challenge using the corresponding public key. Recommendation: Always use a challenge for enhanced security, though it is not strictly required.
1000The customer's UUID (UUID v4). This parameter is useful when a license key is shared among multiple customers, as it allows you to identify individual customers. Note: If strict customers are enabled in your team settings and the license has at least one customer attached, you must provide this value.
The product's UUID (UUID v4). This binds the license key to a specific Lukittu product. Note: If strict products are enabled in your team settings and the license has at least one product attached, you must provide this value.
The version number of your Lukittu product. Useful for tracking which product releases are actively being used. Version must not contain spaces and must be between 3 and 255 characters.
3 - 255