Delete an incident

DELETE

/incidents/{id}

const url = 'https://app.bluelightmaps.com/api/incidents/1';
const options = {method: 'DELETE', headers: {Authorization: 'Basic <credentials>'}};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request DELETE \
  --url https://app.bluelightmaps.com/api/incidents/1 \
  --header 'Authorization: Basic <credentials>'

Delete an incident by its database ID. Every callsign still listed in resources receives an incidentDeassigned event and a stand-down push on each of its devices, so crews are told the job is over. A 202 means the row was deleted but at least one of those devices was offline (push queued for retry) or the callsign could not be resolved. Deleting a closed incident works too; there is simply nothing left to stand down.

Authorizations

BasicAuth
ApiKey

Parameters

Path Parameters

required

integer

Responses

202

Deleted, but some assigned devices were offline or not found

application/json

object

message

string

details

object

deviceStatuses

Keyed by callsign. NOT_FOUND means no device the caller can reach carries that callsign; OFFLINE means at least one of its devices was not online, and that device’s push has been queued for retry. Callsigns whose devices were all online are omitted.

object

key

additional properties

string

Allowed values: OFFLINE NOT_FOUND

Example

{
  "details": {
    "deviceStatuses": {
      "additionalProperty": "OFFLINE"
    }
  }
}

204

Deleted; every assigned callsign was notified

403

The integration user has no permission on this incident

404

Incident not found