The operation records are saved in the lock，Sciener APP will automatically read the records and upload to the cloud server when user use the APP to unlock.
Developers can intergrate the APP SDK to read lock records，and request cloud API:Upload records to upload them to cloud server.
If the lock is WiFi lock or it's connected to gateways, records will be automatically read and uploaded to the cloud by the gateway.
Records uploaded to the cloud can be accessed by this API: Get unlock records.
The lock can save up to 500 records, old records will squeezed out by newer records if exceeded the maximum number. So if the lock is not a WiFi lock and it's not connected to any gateway, you have to read the records by APP in time to avoid losing of records.
The cloud server will save the records in the last six months, earlier records will be archived and can't be accessed.
If the lock is not a WiFi lock and it's not connected to any gateway, the cloud server can't get real-time lock records, so we can't notify the developer.
If the lock is WiFi lock or it's connected to gateways, lock records wil be automatically read and uploaded to the cloud server, the lock's administrator can receive real-time push notification in Sciener APP, and SMS or Email for tamper alert records. And the open platform can push the records to the developer if the developer have set the "Callback URL" field of open platform application, if you want to develop a callback url to receive lock records notification please refer to this doc:Lock Records Notify.
When lock records are uploaded to cloud server, they will be transformed and filtered, the records read from lock by APP SDK may be different from the records get by cloud API: Get unlock records.
The record type description of the original records read by APP SDK from lock please refer to：Record type description from Lock。
The record type description of cloud lock records, please refer to :Record type description of cloud records.