Skip to content
XOS Developers

Delete an incident party

Safety module

DELETE/incident-parties/{id}incidentParties.delete

A person involved in an incident. Soft-deletes the incident party: it moves to Trash and can be restored for its table's retention period.

  • Requires the capability safety.incident.write.
  • OAuth scopes: safety.
  • Error statuses: 401, 404, 422, 429. Errors are RFC 9457 problem details.

Path and query parameters

incidentParties.delete: Path and query parameters
FieldTypeRequiredDescription
idstring (uuid)YesIdentifier of the incident party.

Response 204: no body.

Code samples

curl -X DELETE "$XOS_BASE_URL/incident-parties/0192f1e2-7c3a-7b4d-9e8f-1a2b3c4d5e6f" \
  -H "Authorization: Bearer $XOS_API_KEY"
const { data } = await xos.incidentParties.delete("0192f1e2-7c3a-7b4d-9e8f-1a2b3c4d5e6f");
response = xos.incident_parties.delete("0192f1e2-7c3a-7b4d-9e8f-1a2b3c4d5e6f")
xos incident-parties delete 0192f1e2-7c3a-7b4d-9e8f-1a2b3c4d5e6f