Generation of HMAC, Content MD5 and header for API authentication
Every request to the platform must follow the API Authentication protocol set by Stilt. There are two steps to it
It should pass the correct request header with the expected parameter
It should generate HMAC for every request before it sends to the Stilt Server, as Stilt will reject all the requests that are not coming with a valid header.
A more verbose example of the HMAC creation can be seen on Postman's Collection Pre-Request Script we will provide you to test the APIs. There you can see the HMAC is automatically calculated in runtime for every request sent
For extra security, the HMAC hash will be valid only for 60 seconds. Attempts of using the same HMAC after this time will result in HTTP Status 403: Forbidden
Authentication Header
Using the HMAC method described above platform should add HMAC, Client UUID (Your platform UUID), and EPOCH as a part of the client request.