Apiguide

Video Triggers

Utilizing Video Controls Remotely

Triggers the specified enVision device to perform a video operation by routing the request through enVision Cloud. The enVision device must be registered to enVision Cloud and compatible with remote triggering video capability and be in a video operating mode in order for this method to be supported.

This document describes the specifications of the API endpoint

To see the accessible video operating modes see the documentation here

Start Video

Request the device to begin color video recording. This can be accessed with the following endpoint

/api/remotetrigger/startrecording
Request
curl "https://api.ece.phdsolutions.ca/api/remotetrigger/startrecording?deviceReference=ABCD2345&transactionReference=ORD1234" \
-X GET \
-H "Authorization: Bearer YOUR_AUTH_TOKEN"
You must include a valid Bearer token in the Authorization header of any request to enVision Cloud APIs. Tokens can be managed in the enVision Cloud Portal
Example Response
HTTP/1.1 200 OK
Content-Length: 0
Date: Fri, 16 May 2025 18:34:52 GMT
Server: Kestrel
api-supported-versions: 1.0

Request Parameters

The start video request has multiple optional query strings to help pass custom values and reference transactions.

Note that all optional parameters are only effective in Video Only mode as they will be overwritten otherwise during a measurement.

Required Request Paramaters

PropertyRequiredData TypeDescription
deviceReferenceYesstringthe 8-digit Device Registration Code of the target device. Example: ABCD2345
transactionReferenceYesstringa host-supplied transaction reference for tracking purposes. This can be any value you wish to supply as something that will be tracked with the video operation in enVision Cloud and returned in the response. Possible values are an Order ID, Tracking Number or Barcoded identifier.

Optional Request Parameters

ParameterRequiredData TypeDescription
cRef1Nostringa custom host-supplied reference. This value will be tagged to the transaction stored in enVision Cloud.
cRef2Nostringa custom host-supplied reference. This value will be tagged to the transaction stored in enVision Cloud.
cRef3Nostringa custom host-supplied reference. This value will be tagged to the transaction stored in enVision Cloud.

Stop Video

Requests the video to stop and encode. This endpoint will only work in Video Only mode. To trigger a stop in Video with Measurement mode trigger a measurement (Cloud Trigger). When the video is stopped it will be saved as a transaction to enVision Cloud using the queries called using the Start Video command. The stop endpoint can be accessed at the following location.

/api/remotetrigger/stoprecording
Request
curl "https://api.ece.phdsolutions.ca/api/remotetrigger/stoprecording?deviceReference=ABCD2345" \
-X GET \
-H "Authorization: Bearer YOUR_AUTH_TOKEN"
You must include a valid Bearer token in the Authorization header of any request to enVision Cloud APIs. Tokens can be managed in the enVision Cloud Portal
Example Response
HTTP/1.1 200 OK
Content-Length: 0
Date: Fri, 16 May 2025 18:34:52 GMT
Server: Kestrel
api-supported-versions: 1.0

Request Parameters

PropertyRequiredData TypeDescription
deviceReferenceYesstringthe 8-digit Device Registration Code of the target device. Example: ABCD2345

Cancel Video

Requests the video to stop and clear all saved video data in memory and local storage on the specified device. This can be accessed at the following endpoint

/api/remotetrigger/cancelrecording
Request
curl "https://api.ece.phdsolutions.ca/api/remotetrigger/cancelrecording?deviceReference=ABCD2345" \
-X GET \
-H "Authorization: Bearer YOUR_AUTH_TOKEN"
You must include a valid Bearer token in the Authorization header of any request to enVision Cloud APIs. Tokens can be managed in the enVision Cloud Portal
Example Response
HTTP/1.1 200 OK
Content-Length: 0
Date: Fri, 16 May 2025 18:34:52 GMT
Server: Kestrel
api-supported-versions: 1.0

Request Parameters

PropertyRequiredData TypeDescription
deviceReferenceYesstringthe 8-digit Device Registration Code of the target device. Example: ABCD2345

HTTP Response Status Codes

All requests have the following response status codes

Status CodeDescription
200 - OKThe request was successfully routed to the target device and a response was provided in the body of the HTTP response.
400 - Bad RequestThe device reference Id provided was not valid.
401 - UnauthorizedThe bearer token provided was not valid.
504 - TimeoutThe remote device did not respond in a timely manner.

Copyright © PHD Solutions 2024