Unlock locks

Cloud unlocks allow your application to remotely unlock doors by making direct API calls using admin credentials. This is the simplest integration method when you need basic unlock functionality without managing individual user accounts or credentials.

Unlock a lock

1. Send a POST request to the unlock lock endpoint.

Example

curl --request POST \
  --url https://api.kisi.io/locks/{id}/unlock \
  --header 'Authorization: KISI-LOGIN <API_KEY>' \
  --header 'Content-Type: application/json' \
  --data '{
  "context": {
    "location": {
      "longitude": 0,
      "latitude": 0
    }
  },
  "lock": {
    "proximity_proof": null
  }
}'

• id (in URL path) - the ID of the lock to unlock
• context.location (optional) - the user's current location for geo-fence restricted locks. Uses WGS 84 coordinate system with longitude and latitude values
• lock.proximity_proof (optional) - proximity proof to verify proximity to lock. Required for locks with proximity restrictions. Can be null if not needed

tip

For most locks, you can copy this example and simply replace {id} with your lock ID and <API_KEY> with your API key to unlock doors. The proximity_proof and location context are only needed if your locks have geo-fence or proximity restrictions enabled.

Response

If your request was successful, you'll receive a 200 OK response confirming the unlock.

{
  "message": "Unlocked!"
}

note

The duration of the unlock is determined by the lock's hardware settings, not by the API request.

Unlock events

All unlock requests made via this endpoint appear in your organization's audit logs as admin actions. The unlock event is attributed to the admin account that owns the API key, not to individual end users.

If you need unlock events attributed to specific users, consider using the user unlock integration method instead.