Using /api/rest/v1/alarms POST and tag element support 2023 R3

MIP
, , , ,
1

Is there a known issue with using /api/rest/v1/alarms and specifying a tag value. I am using XProtect 2023 R3 and find that the tag value is not assigned to the generated alarm. Also, when getting alarms the tag element is not included in the response.

I see that the tag element is defined in the https://doc.developer.milestonesys.com/mipvmsapi/api/alarms-rest/v1/#tag/Alarms/operation/Alarms_Post endpoint.

2

The documentation is misleading. The Tag was introduced in version 24R2, there have been created a task to update the documentation to show when it was available from.