A direct gRPC request can be anonymous. If an HTTP request is made to a web server, then it is necessary to use the Basic authorization type, since the anonymous requests to the web server are prohibited.
token_value − a Bearer token. The received token should be used in the metadata of the gRPC request. The HTTP requests should be made with the Bearer authorization type using the received token.
expires_at − token expiration date and time in the UTC time zone.
where uid is the Server where the device is created.
As a result, a camera with a child microphone, an embedded archive and a sensor will be created. All child objects except the video channel will be turned off.
The response will contain the page_token parameter if the number of archives (including the built-in ones) is greater than the value of the page_size parameter.
The response will contain the page_token parameter if the number of archives (including the built-in ones) is greater than the value of the page_size parameter.
timezone_id − id of the time zone. If 00000000-0000-0000-0000-000000000000, then the time zone is Always.
supervisor − id of the role that will be a supervisor (see Creating and configuring roles). If 00000000-0000-0000-0000-000000000000, then the supervisor is not defined.
dt_posix_end_time and dt_posix_start_time specify the interval,
image_size is the image size.
Note
To get the coordinates of the objects movement, it is necessary to specify the RESULT_TYPE_DATA value for the result_type parameter in the request body.
If descending = false, then the events in the response will be sorted by time in ascending order. If descending = true, then the events will be sorted in descending order.
limit – the limit of events in the response.
Get events by filter
The following parameters can be set as a filter:
type –type of event; the actual types of events are given in the axxonsoft\bl\events.proto file;
subjects –subject of event (server, device, archive, detector, etc.);
values –exact value of event;
texts –brief description of event.
Get events about status change of a specific camera
subscription_id − subscription ID (set arbitrarily in UUID format; mandatory parameter).
event_type – event type (optional parameter).
subject – subject of the event (detectors in this example; optional parameter).
To receive events using a subscription, do the following:
Run a request with the PullEvents method. After receiving the "200 OK" response, the events will be accumulated.
After the required time interval, run a request with the DisconnectEventChannel method. You will receive a list of events that occurred between the two requests.
The request body with the DisconnectEventChannel method:
Templates allow you to apply the same preset parameters to cameras.
Note
If a template has been assigned to the camera but has not yet been applied, then the response to the ListUnits method (see Manage devices using gRPC API methods (ConfigurationService)) will contain the parameter "has_unapplied_templates": true.