We are working on REST API and it will go out as pre-release right after 2021 R2 release. Please keep eye on a news from Milestone.
Any news on this?
Its getting closer to production release - check out the link below. You can test the latest bits by installing the API bridge with a 2021 R2 Management Server. There’s still work to be done, but the shape of the configuration rest api is unlikely to change much between now and release.
I tested autorest against the openapi definition to generate a PowerShell client module but it threw some errors. The SDK team sent a new definition my way for testing so I’ll try that out on Monday.
Still, most of the raw API calls I’ve tried have worked as expected. There are a few little things that are really obvious to users of the api that would have been easy to miss while developing and iterating on the new api like Boolean enabled/disabled filters that need to be passed as quoted strings instead of plain Boolean values. Those are the kinds of things that are likely to change/improve between now and official release in 2022 R1.
I’m browsing the REST API documents and don’t see a way to query alarm history. I see very clearly how to fetch alarm definitions, but not how to get info on when those alarms where triggered/closed. Am I missing something or is that out of scope of the REST API in this first version?
It is out of scope of this version of the Rest API, what is currently supported is the functionality that is also in the Configuration API, as the name indicate the data that configures XProtect. On the future road map is to introduce newer and more modern APIs on all the data on XProtect..
Hi Bo, is there any timeline/roadmap when events/alarms wil be implemented to the REST API?
REST API – Events and Alarms are not prioritized yet but we definitely see the need and the value of the impact area for REST API.