What is the Beacon API?
This resource is intended for asset tag manufacturers (also known as proximity beacon providers) to submit the list of tags that have been successfully tested and dispatched to Microlise. Below is the list of information required by Microlise to successfully process the data.
a. MAC ID
b. Date of test – to be considered as the DOB of the beacon.
c. Firmware version – never going to change
d. Battery Voltage- in Volts
e. Serial Number (Microlise or JCB)
f. Item Code
Who should use the API? – Manufacturers of asset tags for Microlise.
Any dependencies? – No Dependencies
Steps to Integrate
Navigate to the ‘Products’ tab (a product being a singular or collection of APIs) then ‘Truly Wireless'.
To access the API you will need to request and be issued an API Key via secured email. The key should be passed in the HTTP header using the x-api-key custom header.
You can test the API Key in the Try it feature of the Beacon API from the API List.
Rate limiting:
Maximum 60 request per min allowed from single IP.
In each request, maximum you can specify 25 beacon information.