⚠️ Linux only. Custom actions apply exclusively to Linux-managed devices. This endpoint is not applicable to Android, iOS, or Windows devices.

Permanently deletes a custom action by its unique ID. Returns HTTP 200 on success. Returns 400 if the custom action is currently in an active state — active custom actions must be deactivated before they can be deleted. Returns 404 if the custom action does not exist. Deletion is irreversible and removes the action and all its associated option scripts.

About Delete Custom Action

Custom actions define scripts that can be embedded in Blueprint V2 configurations and deployed to Linux devices. Deleting an active custom action is blocked to prevent accidental removal of actions currently referenced in live blueprints. Before deleting, transition the action to inactive or draft state using PUT /v2/custom-actions/{custom_action_id}/, then verify it is not referenced by any active blueprints.

Key Fields

custom_action_id — UUID of the custom action to delete (path parameter, required)

Common Use Cases

Remove a deprecated or unused custom action after it has been replaced by a newer one

Clean up test or draft custom actions that are no longer needed

Decommission a custom action tied to a retired Linux device workflow

Best Practices

Before deleting, update the action's state to inactive via PUT /v2/custom-actions/{custom_action_id}/ — the API blocks deletion of active actions (returns 400)

Confirm that no active Blueprint V2 configurations reference this custom action before deleting

Archive the script content by calling GET /v2/scripts/{script_id}/ for each option's script if you may need it later

Workflow

If the action is active, update it to state: "inactive" via PUT /v2/custom-actions/{custom_action_id}/

Verify that no live Blueprints reference this custom action

Call DELETE /v2/custom-actions/{custom_action_id}/

Confirm HTTP 200 response; the action will no longer appear in GET /v2/custom-actions/ results