Mission Control Web API privileges - Mission Control 3.1.2.0

Genetec Mission Controlâ„¢ Deployment Guide 3.1.2.0

Applies to
Mission Control 3.1.2.0
Last updated
2023-11-23
Content type
Guides > Deployment guides
Language
English
Product
Mission Control
Version
3.1

The Web API interacts with Genetec Mission Controlâ„¢ as a Security Center user. This user requires privileges to perform Web API commands.

The Web API uses the following Security Center privileges to control access:
Privilege Endpoint Description
Log on using the SDK All Allows applications to authenticate with Mission Control using the Web API.
Third-party integration mode All Allows applications using the Web API to bypass some system validations and interact with incidents without restrictions.

It has the following effects:

  • Web API commands bypass certain system requirements:
    • Having incident ownership
    • Following the incident state flow
    • Being an incident recipient
    • Having the required privileges
  • Web API commands that bypass system requirements do not cause side effects, such as taking incident ownership.
  • The Web API user can query any active incident on a location they have access to.
  • The Web API user can trigger any In service incident type on a location that they have access to.
  • The Web API user can receive notifications related to any active incident.
Trigger incidents POST /V2/Incidents Allows applications to trigger incidents using the Web API.
Link incidents POST /V2/Incidents Allows applications to link and unlink incidents using the Web API.
Add incident comments POST /V2/Incidents/{id} Allows applications to add incident comments using the Web API.
Edit or delete incident comments POST /V2/Incidents/{id} Allows applications to change or delete incident comments using the Web API.
Change incident description POST /V2/Incidents/{id} Allows applications to change the description of an incident using the Web API.
Change incident priority POST /V2/Incidents/{id} Allows applications to change the priority of an incident using the Web API.
Take incident ownership POST /V2/Incidents/{id} Allows applications to take or release ownership of incidents using the Web API.
NOTE:
  • The Modify reported incidents (Mission Control) or the Third-party integration mode privilege is required to change closed incidents.
  • The Incident report privilege is required to see closed incidents or incidents that the user is not a recipient of.
  • The Incidents (Mission Control is required to see incidents retrieved through the GET /V2/Incidents or GET /V2/Incidents/{id} endpoints.