Audit Trail

Every Connected Lock stores a rolling list of history events. When a lock is able to communicate via Bluetooth with the iOS or Android framework, these history events are automatically read and reported through a delegate to the application. These events will provide information on when a lock is used and by whom.

There is no API to retrieve the audit trail. This must be retrieved through the SDK delegate. Master Lock does not store any of these events.

For a complete list of the audit events recorded by a lock, see the following pages:

• iOS (Swift)
• iOS (Objective-C)
• Android Delegate
• Android Enumerations

Troubleshooting

If the audit trail delegate is not being called:

• Ensure that your access profile has the AuditTrail permission.
• Make sure you are on the latest version of the SDKs.
• Potential networking issues: Before the delegate is called, the SDK must be able to complete a web request to vesdk.masterlockvault.com. Please ensure that there is internet connectivity and there are no networking rules that prevent this request.