DOTA PUSH / PULL Integration with our server

In order to access any data the sensors are producing, you can either visually observe them via our web application DOTA, or integrate your information system with our REST API.

There are basically two possibilities:

HTTP PUSH (recommended) – meaning that our server will notify your systems imediately always when a parking slot changes its state (from FREE to BUSY, or vice versa). It will send a HTTP POST request to your URL, carrying the data in the form of a JSON (format specification here).
HTTP PULL (not recommended) – meaning, that your system shall regularly check for any changes on our server. After an initial authentication HTTP GET call (e.g. via CURL), where a session_id is obtained (valid for 60 minutes), your system shall execute a second HTTP GET call, to obtain the data again in the form of a JSON (format specification here).

We strongly recommend to use the first method: PUSH messages, that are event-based.

Main advantage of PUSH messages is that you don’t have to care about session acquisition and validity, as you have to do in the case of PULL messages.

We recommend PUSH mesages, because PULL calls generate a lot of unnecesary traffic, especially if you would like to check for new data too often.

Please consult our swagger page for further details on JSON structure.