When a Service Provider attempts to create a Key for a Lock who's Lock Holder's Vendor Connection is in an error state, a 403 error code will be returned. Previously the Key creation endpoint returned 200 regardless of the Vendor Connection state.
Locks returned from the endpoint Return list of all locks in the Service Provider API now include a
lockHolder field. This aims to make it easier for you, as a Service Provider, to distinguish Locks that you can create Keys for.
- It is now possible to create a virtual Vendor Connection specifying an amount of virtual Locks to create
- Locks returned from the API now contain a
createdfield specifying the creation date using the ISO-8601 format
- It is now possible to sort Locks in the Get all Locks From a Lock Holder endpoint by
created, either by ascending or descending order
We have added two new endpoints:
We've changed what service we host our API on, making it considerably more responsive.
Most endpoints should respond in around 400ms (unless you're fetching a lot of data), and the horrible 4-5 second spikes should be completely gone.
The old way of getting a lockholder in scope was to use lockHolder.identifier:[countryIso].[orgId].[orgIdSuffix], e.g. lockHolder.identifier:NO. 919424508.test.
We have just launched a new endpoint to close a Key Request. Closing a Key Request will revoke any keys associated with it.
We have just launched a new product for the Service Provider API. Through the API it is now possible to request digital keys from a user. Use it to enable in-home delivery and similar.
We have added documentation on how to handle Secure Devices in the Service Provider API. Secure device is a concept introduced in order to maintain control over which service provider devices are used to interact with keys to privately owned locks from the Unloc Work app. A typical use case is a service partner that wishes to get access to a users apartment, to perform some service.