Solved

How to get `status` for Endpoints via API?

  • 21 February 2019
  • 4 replies
  • 317 views

Badge +2
Hi,

Is there a way to figure out via API the `status` values for Endpoints that I can see at the website under **Endpoint Protection > Group Management **?

Ive tried all APIs but couldnt get the info..

icon

Best answer by ngoknel 24 May 2019, 12:40

View original

4 replies

Userlevel 4
Badge +9
Hi @rhasan,

Please take a look at this API Documentation for details on how to accomplish this. If you run into any issues please feel free to open a ticket with our support team.

Best regards,
Joseph R.
Product Manager, Integrations
Badge
Hi!

Similarly to the thread creator, we're trying to access the "Protected" flag for each site and/or endpoint through the Unity API, but can't seem to figure out which value this represents. We've tried checking multiple values but it doesn't seem to correlate. Can you please advise how to get this information, as the API documentation doesn't really cover this and we can't seem to find a value that matches the information that we see in Webroot?

Thanks in advance!

Best regards, Richard
Userlevel 3
Badge +8
Hey Richard Johansson,

The "Protected" status is purely a endpoint console generated state based on other states from the endpoint. For example, if the endpoints "Last Seen" date is less than 7 days, its not currently in an "Infected" or other non-clean state and has not been "deactivated", the "Protected" state is set.

Hope this makes sense,
Nick G
Badge
Hey Richard Johansson,

The "Protected" status is purely a endpoint console generated state based on other states from the endpoint. For example, if the endpoints "Last Seen" date is less than 7 days, its not currently in an "Infected" or other non-clean state and has not been "deactivated", the "Protected" state is set.

Hope this makes sense,
Nick G



Ah, alright. I think that's enough for us to build a similar logic on our end that will work for our use case. Thank you for the very swift and informative answer!

Best regards,
Richard

Reply