From d7664cca4483b7c1a2a2cdf296f96da3cfd92287 Mon Sep 17 00:00:00 2001 From: Marko Oldenburg Date: Mon, 29 Nov 2021 13:02:50 +0100 Subject: [PATCH] =?UTF-8?q?=E2=80=9ENUKI=20DEVELOPER=20|=20Nuki=20Bridge?= =?UTF-8?q?=20HTTP=20API=E2=80=9C=20=C3=A4ndern?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- NUKI-DEVELOPER-%7C-Nuki-Bridge-HTTP-API.md | 34 ++++++++++++++++++++++ 1 file changed, 34 insertions(+) diff --git a/NUKI-DEVELOPER-%7C-Nuki-Bridge-HTTP-API.md b/NUKI-DEVELOPER-%7C-Nuki-Bridge-HTTP-API.md index 8c21e0f..8cf8087 100644 --- a/NUKI-DEVELOPER-%7C-Nuki-Bridge-HTTP-API.md +++ b/NUKI-DEVELOPER-%7C-Nuki-Bridge-HTTP-API.md @@ -154,3 +154,37 @@ Possible doorsensor states (used in Endpoints below). ## 5. Endpoints ### /auth + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
URLhttp://192.168.1.50:8080/auth
UsageEnables the api (if not yet enabled) and returns the api token. If no api token has yet been set, a new (random) one is generated. When issuing this API-call the bridge turns on its LED for 30 seconds. The button of the bridge has to be pressed within this timeframe. Otherwise the bridge returns a negative success and no token.
ResponseJSON list containing the success of the authorization
tokenThe api token
successFlag indicating the success of the authorization
ErrorsHTTP 403Returned if the authentication is disabled
Example-Callhttp://192.168.1.50:8080/auth
Example-Response{ "token": “token123”,"success": true}
\ No newline at end of file