Delete a SOP
Knowledge module
DELETE/sops/{id}sops.delete
A standard operating procedure that members acknowledge. Soft-deletes the SOP: it moves to Trash and can be restored for its table's retention period.
- Requires the capability knowledge.sop.write.
- OAuth scopes: knowledge.
- Error statuses: 401, 404, 422, 429. Errors are RFC 9457 problem details.
Path and query parameters
| Field | Type | Required | Description |
|---|---|---|---|
| id | string (uuid) | Yes | Identifier of the sop. |
Response 204: no body.
Code samples
curl -X DELETE "$XOS_BASE_URL/sops/0192f1e2-7c3a-7b4d-9e8f-1a2b3c4d5e6f" \
-H "Authorization: Bearer $XOS_API_KEY"const { data } = await xos.sops.delete("0192f1e2-7c3a-7b4d-9e8f-1a2b3c4d5e6f");response = xos.sops.delete("0192f1e2-7c3a-7b4d-9e8f-1a2b3c4d5e6f")xos sops delete 0192f1e2-7c3a-7b4d-9e8f-1a2b3c4d5e6f