Using LiveResponse API you will be able to collect data from LiveResponse and use it in other applications through the calls we describe in the API documentation.
In order to use LiveResponse API, you need an API-key for the organization whos data you want to access. The API-key can be generated by the organization under Settings / API in the LiveResponse web application.
LiveResponse API can be called through either GET or POST over HTTP, depending on what API-method you want to access.
Authentication is made by passing a valid API-key as part of the URL, when calling any of the API-methods.
The key should be passed as the querystring-parameter key.
Response format negotiation
The format of the response is negotiated through the HTTP Accept header. Currently the API support JSON and XML.
The accept-header should therefore be set to either application/json or application/xml
/video/all - HTTP GET
Allow you to fetch meta-data about a given number of your organizations videos.
||Number of videos to display. Possible interval: 1-100.
||Used in combination with limit, to page through the videos. Possible interval: 1-.
GET http://app.liveresponse.se/api/video/all?key=XXXXXXXXXXXXXXXX&limit=100&page=1 HTTP/1.1
Sample response JSON:
Sample response XML:
/video/position - HTTP POST
Allow you to specify the current geographical position of a given camera. This will update the geographical position
of all videos broadcasted by the camera within the last minute. It will also set the geographical position of all videos
broadcasted by the camera within a minute after the position has been received.
||A unique ID of the camera you want to specify the position for. If you don't know the ID
of your camera, please contact our support.
||The current latitude of the camera, given in WGS84.
||The current longitude of the camera, given in WGS84.
POST http://app.liveresponse.se/api/video/position?key=XXXXXXXXXXXXXXXX HTTP/1.1
If the call is successful you will recieve a HTTP 204 No content, in response.
Unsuccessful calls will result in an HTTP 500, where the HTTP body may contain a more detailed description of the error.