License API Authorization
To ensure the integrity of server requests, every request must be signed. The signature serves as a unique representation of the request and is included in the Authorization header.
The signature is generated using a specific algorithm applied to the request parameters. The resulting value is a canonicalized signing string, ensuring the request's authenticity.
Each client request must include the following headers:
Date
Current time given as a date string in RFC7231 format. Note that this value is always in the GMT timezone.
Example: Date: Tue, 07 Jun 2014 20:51:35 GMT
Authorization
This header contains information on how the request is authorized:
- algorithm: Defines the signature hashing algorithm, by default hmac-sha256
- headers: Defines the headers used to derive the signature, set this to date
- apikey: The API key used for the request
- signature: The Base64-encoded value of the signing string. See the specification is on the Request Signature page.
Example Authorization header:

Ensure that the Date header value is set to current time. The server allows timestamps that are up to 15 minutes old.

