Go to documentation repository
Documentation for Axxon One 1.0.
Previous page
Next page
GET http://IP Address:port/prefix/archive/events/detectors/{ENDTIME}/{BEGINTIME} − get detections from all Axxon-domain Servers.
Note
The ENDTIME and BEGINTIME syntax is described in Get archive contents section.
Attention!
If ENDTIME < BEGINTIME in the request, then the events in the response will be sorted by time in ascending order.
If ENDTIME > BEGINTIME, then the events will be sorted in descending order.
GET http://IP Address:port/prefix/archive/events/detectors/{HOSTNAME}/{ENDTIME}/{BEGINTIME} – get detections from a certain Server.
{HOSTNAME} – Server name (see Get Server list).
GET http://IP Address:port/prefix/archive/events/detectors/{VIDEOSOURCEID}/{ENDTIME}/{BEGINTIME} – get detections from a certain camera.
{VIDEOSOURCEID} – three-component source endpoint ID (see Get list of video cameras and information about them). For instance, "SERVER1/DeviceIpint.3/SourceEndpoint.video:0:0".
| Parameter | Required | Description |
|---|---|---|
| limit | No | Limit of detections in the response. If not specified, it is equal to 100. |
| offset | No | The results offset by the specified number. For example, if a query with offset=0 returned 100 results, then in order to get the next results, it is necessary to run a query with offset=100. If the second query returned 250 results, then in order to get the next results, it is necessary to run a query with offset=350, etc. |
| type | No | Get detections from a certain detection tool. The parameter values are listed in the table below. |
| join | No | If join=1, then in the response, the two-phase events will be merged together, and the duration parameter will be returned which corresponds to the event duration. If join=0, then in the response, the two-phase events will not be merged together. |
| limit_to_archive | No | If limit_to_archive=1, then the response will return the events only from the accessible part of the archive (see Configuring access restrictions to older footage). |
| archive | No | The name of the archive from the request to receive the list of archives (see Get archive contents). |
Sample requests:
http://127.0.0.1:80/archive/events/detectors/Server1/DeviceIpint.2/SourceEndpoint.video:0:0/past/future?limit=10&offset=0 – get detections from a certain camera, sorted in descending order. The maximum limit is 10.
http://127.0.0.1:80/archive/events/detectors/Server1/past/future?limit=5&offset=0 – get detections from all detection tools of Server1. The maximum limit for each detection tool is 5.
http://127.0.0.1:80/archive/events/detectors/Server1/past/future?limit=5&offset=0&type=Ray – get detections from all sensors of Server1. The maximum limit for each sensor is 5.
http://127.0.0.1:80/archive/events/detectors/past/future?limit=1&type=Ray – get the current state of all sensors of the Axxon-domain.
Sample response:
Attention!
By default, the request timeout is 10 seconds.
If the Server fails to return all events (the quantity is set in the limit parameter) in 10 seconds, the response will be as follows:
{
"events": [],
"more": false
}
In this case, it is necessary to repeat the request and reduce the value of the limit parameter.
Note
The multiPhaseSyncId parameter will be in the response only for two-phase alarms with alertState parameter.
Field timestamp is not unique so it might be necessary to skip the previously received alarms starting from the search interval.
When requesting the queue detection tool triggerings, the response includes an additional extra parameter that contains the queue length estimate expressed by the minimum and maximum values.
{
"alertState": "happened",
"extra": [
{
"queueMax": "4"
},
{
"queueMin": "4"
}
],
"id": "b17129b2-1588-794b-94f6-d078a226efb2",
"origin": "hosts/Server1/AVDetector.4/EventSupplier",
"rectangles": [],
"source": "hosts/Server1/DeviceIpint.2/SourceEndpoint.video:0:0",
"timestamp": "20181206T075621.621000",
"type": "QueueDetected"
}
}
Available values of type parameter:
| Detection tool | type |
|---|---|
| Scene Analytics detection tools | - |
| Line crossing | oneLine |
| Motion in area | moveInZone |
| Stop in area | stopInZone |
| Appearance in area | comeInZone |
| Disappearance in area | outOfZone |
| Loitering | longInZone |
| Multiple objects | lostObject |
| Number Plate Recognition | plateRecognized |
| Number Plate Recognition (from the list) | listed_lpr_detected |
| Face detection | faceAppeared |
| Face detection (from the list) | listed_face_detected |
| Visitors counter | PeopleIn, PeopleOut |
| Queue detection | QueueDetected |
| Fire detection | FireDetected |
| Smoke detection | SmokeDetected |
| Neural counting | lotsObjects |
| Position change | SceneChangeDetected |
| Image Noise Detection | CameraBlindDetected |
| Loss of quality | ImageDegradation |
| Blurred Image Detection | BlurredDegradation |
| Compression Artifacts Detection | CompressedDegradation |
| Motion detection | MotionDetected |
| No signal | NullAudio |
| Signal | SignalAudio |
| Noise | NoiseAudio |
| Pose detection | - |
| Man down detection | recumbent |
| Sitting person detection | sitDown |
| Hands up detection | handsUp |
| Water level detection | LevelOut |
| Handrail holding detection | handRail |
| People counter | lotsObjects |
| Close-standing people detection | peopleDistance |
| People masking | enabledMaskEvents |
Note
If the non-included in the list value is received, then an embedded detection tool triggered.
Important!
Case sensitivity of detector triggering types is not guaranteed. For instance, 'ComeInZone', 'comeInZone' and 'COMEINZOne' values are to be considered as the same ones.
Overview
Content Tools