The protocol is based on HTTP/1.1. The same endpoint (URL) is used for
all operations. The data is sent using
“application/x-www-formurlencoded” encoding.
In order to prevent malicious usage, the protocol access should be
authenticated. BASIC HTTP authentication is supported (see the section 2
of RFC 2617). It is required
to use HTTPS protocol to protect login/password from being intercepted.
There are two types of the protocol implementation:
| Name | Description | License Billing Conditions | Supported Requests |
|---|---|---|---|
| Standard |
Intended for managing regular third-party licenses. Example: an application that scans the server for |
One license per server/instance. Each active license is a subject for billing with the flat SKU/price. |
|
| With reporting |
In addition to what is possible with “standard”, it can be also Typically this type of protocol is used for licensing access to Example: an application that stores backups in the cloud (a |
One license per server/instance. Each license is free and is used for identifying the Plesk server instance for usage tracking. License can be considered as a container for certain resource usage counters. Each such counter is used for billing a customer at the flat SKU/price multiplied by the counter itself. |
|