Bridge HTTP-API

1. Introduction

The Bridge API offers simple endpoints to list all available Nuki Smart Locks,
retrieve their current lock state and perform lock operations.
When using the Nuki Software Bridge, all configuration is done inside the Nuki Bridge App instead
of the Nuki App.

2. Calling URL

This is the address used to call the available services of the internal webserver.
The IP address is shown in the bridge settings within the Nuki App or can be retrieved from the
bridge discovery URL.
The server is listening for incoming requests either on default port 8080 or the configured one if it
has been modified within the Nuki App.

3. Example

The following base url will be used in upcoming examples:
http://192.168.1.50:8080/

4. Bridge discovery & API activation

See: Bridge discovery & HTTP-API activation

5. Lock states

See: https://developer.nuki.io/page/nuki-bridge-http-api-110/4/#heading--states-actions

6. Endpoints

See: https://developer.nuki.io/page/nuki-bridge-http-api-110/4/#heading--endpoints

Latest PDF-Version

Download as PDF

This topic will contain a table of contents

I do have the hardware bridge v2 and the discovery also does not show the IP address and any request I send cannot be opened by safari as “the server is not responding”.

The use of the API however works via my DoorBird integrated features but I need to add some extra communication with my Loxone Miniserver to enable and disable my alarm system. I would also like to unlock the Nuki via the DoorBird NFC transponder.

Thanks

According to the bridge API, there’s a command for Lock n go Unlatch

That no longer seems to work the way it used to earlier. Now when sending the command, it only unlatches, but doesn’t relock. Is this is an intentional change?

There is only one lock action for lock’n’go which pulls the latch based on the handle settings of the Smart Lock.
There are separate unlatch/ubloxk lock actions though to override this setting, but not explicitly for l’n’g.