From 46b701b1e24d9ea0c77af2ae9932e9fdff22f1dd Mon Sep 17 00:00:00 2001 From: Marko Oldenburg Date: Tue, 30 Nov 2021 09:56:17 +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 | 43 ++++++++++++++++++++++ 1 file changed, 43 insertions(+) diff --git a/NUKI-DEVELOPER-%7C-Nuki-Bridge-HTTP-API.md b/NUKI-DEVELOPER-%7C-Nuki-Bridge-HTTP-API.md index ad52d32..f8b2db7 100644 --- a/NUKI-DEVELOPER-%7C-Nuki-Bridge-HTTP-API.md +++ b/NUKI-DEVELOPER-%7C-Nuki-Bridge-HTTP-API.md @@ -187,4 +187,47 @@ Possible doorsensor states (used in Endpoints below). Example-Response {"token": “token123”,"success": true} + + +### /configAuth + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
URLhttp://192.168.1.50:8080/configAuth
UsageEnables or disables the authorization via /auth and the publication of the local IP and port to the discovery URL (https://api.nuki.io/discover/bridges).
URL-ParametersenableFlag (0 or 1) indicating whether or not the authorization should be enabled
tokenThe api token configured via the Nuki app when enabling the API
ResponseJSON list containing the success of the operation
successFlag indicating the success of the authorization
ErrorsHTTP 400 + Returned if the given value for enable is invalid (neither 0 nor 1)
HTTP 401Returned if the given token is invalid or a hashed token parameter is missing.
Example-Callshttp://192.168.1.50:8080/configAuth?enable=0&token=123456 +http://192.168.1.50:8080/configAuth?enable=0&ts=2019-03-05T01:06:53Z&rnr=4711&hash=f52eb5ce382e356c4239f8fb4d0a87402bb95b7b3124f0762b806ad7d0d01cb6
\ No newline at end of file