Skip to main content

deassignAlert

A Graze API POST request that deassigns the current owner from the specified alert, and leaves it unassigned.

Back to Graze API EndPoint Reference.

Request arguments

Endpoint deassignAlert takes the following request arguments:

Name

Type

Required

Description

auth_token

String

Yes

A valid auth_token returned from the authenticate request. Alternatively, basic authenticate headers can be used in place of this parameter. See the authenticate endpoint for more information and usage examples.

alert_id

Number

Yes

ID of the alert that you want to deassign the owner from.

Response

Endpoint deassignAlert returns the following response:

API update behavior

The behavior of this endpoint depends on whether the relevant alert or Situation is open, closed and still in the active database, or closed and archived to the historic database. This endpoint updates the alert or Situation as follows:

See API Update Behavior for more information on Situation statuses.

Examples

The following examples demonstrate typical use of endpoint deassignAlert:

Request example

Example cURL request to deassign the current owner from alert ID 7:

curl -X POST -u graze:graze -k -v "https://localhost/graze/v1/deassignAlert" -H "Content-Type: application/json; charset=UTF-8" -d '{"alert_id" : 7}'

Response example

In this section: