Accessing the dSS¶

The dSS is accessible through a HTTP based JSON interface as well as through SOAP. Applications accessing the dSS must not store any passwords at any time. Instead they should request an application-token which has to be acknowledged by the user.

Getting a token¶

An application needs to get a token from the dSS.

https://yourdss:8080/json/system/requestApplicationToken?applicationName=readable%20Name%20of%20application

Note that the application must not be logged in or access the dSS through the default HTTPS port.

Approving the token¶

The User needs to be redirected to the dSS webinterface where he can approve the token. Page pending, see #848

Logging in¶

After the token has been approved the application may obtain a session-token by providing the application token:

https://yourdss:8080/json/system/loginApplication?loginToken=yourtokenhere

Using the session token¶

Add the token to the http header, or add "token=yoursessiontokenhere", fx:

https://yourdss:8080/json/apartment/getStructure?token=yourtokenhere

The session token has a timeout of 60 seconds, but will be prolonged each time it is used/touched.
If the session token is invalid, a new session token should be acquired.