Check Bundle

Endpoint

  • Method: GET

  • Path: /api/v4/check_bundle

  • Description: Checks the status and validity of a license bundle.

Authentication

See License API Authorization.

Required headers

  • Date (string) — RFC7231 GMT date string

  • Authorization (string) — signature or bearer token

  • Accept: application/json

Request

Query parameters

Required:

  • hardware_id (string)

  • product (string) — Bundle product short code

One of:

  • license_key (string)

  • username (string)

Optional:

  • license_id (number)

  • include_expired_features (boolean)

  • env (string)

  • os_ver (string)

  • hostname (string)

  • os_hostname (string)

  • ip (string)

  • ip_local (string)

  • app_ver (string)

  • sdk_ver (string)

  • mac_address (string)

Examples


Schema

Request Query Parameters

chevron-rightRequest schema (TypeScript + JSON Schema)hashtag

TypeScript

JSON Schema


Response Body

chevron-rightResponse schema (TypeScript + JSON Schema)hashtag

TypeScript

JSON Schema


Response Signatures

The response objects contain the following digital signatures:


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

Each license assigned to the product requires the client to provide a license key in order to activate, check or deactivate the license (property license_key in the request). The license response object will contain the license_key property, and product_details.authorization_method will be "license_key".

User-based product licenses

Each license assigned to the product has a corresponding "license user" instead of a license key. Requires username to be provided. In the license response object, product_details.authorization_method will be "user" and the response object will contain the user object with information on the license user.


License Types

The license_type property defines one of the 4 types of licenses based on their duration and how the license is used:

  • perpetual: "perpetual"

  • time-limited: "time-limited"

  • subscription: "subscription"

  • consumption: "consumption"

For more information see: License Types


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:

chevron-rightError schema (TypeScript + JSON Schema)hashtag

JSON Schema

List of exceptions

chevron-rightmissing_headers (400)hashtag

Some headers are missing

chevron-rightunknown_product (400)hashtag

Provided product was not found

chevron-rightlicense_not_found (400)hashtag

License with the provided license user not found

chevron-rightlicense_not_enabled (400)hashtag

The license is not enabled

chevron-rightlicense_not_active (400)hashtag

The license is not active

chevron-rightdevice_not_found (400)hashtag

An active device matching the hardware_id not found

chevron-rightblacklisted (400)hashtag

This device is blacklisted

chevron-rightlicense_not_enough_consumptions (400)hashtag

Not enough consumptions left

chevron-rightfloating_not_available (400)hashtag

No available slots for floating license

Last updated

Was this helpful?