License API
Consumption

Add Feature Consumption

10min
Adds 1 or more consumptions to a license feature (only for licenses with consumption features)
POST
Request
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
Body Parameters
hardware_id
required
String
Unique hardware ID generated for the client device
product
required
String
Product short code
feature
required
String
Feature 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"
consumptions
optional
Number
Number of consumptions to add, defaults to 1. May be negative, unless `allow_negative_consumptions` is set to false
Curl
Node.js
JS
Python
Ruby
Responses
200
400


Schema

Request Body

TypeScript
JSON


Response Body

TypeScript
JSON


License Authorization Method

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

Errors

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:

TypeScript


List of exceptions

unknown_product (400): Provided product was not found
license_not_found (400): License with the provided license user not found
license_not_active (400): The license is not active
license_not_enabled (400): The license is not enabled
unsupported_product_feature (400): One or more of requested product features do not exists or they are not enabled on the product
feature_not_enough_consumptions (400): Not enough consumptions left
negative_consumptions_not_allowed (400): Negative consumptions not allowed
device_not_found (400): An active device matching the hardware_id not found
blacklisted (400): This device is blacklisted



Updated 17 Jan 2025
Doc contributor
Doc contributor
Doc contributor
Doc contributor
Doc contributor
Did this page help you?