Delete SSH Monitor

DELETE /api/ssh-monitors/:sshMonitorPublicId

AuthenticationCopy Anchor Link

Requires a valid session and write access.

• Header: Authorization: Bearer <token>

ParametersCopy Anchor Link

• sshMonitorPublicId (Path, required): SSH monitor public UUID.

cURLCopy Anchor Link

curl -X DELETE "https://YOUR_DOMAIN/api/ssh-monitors/44444444-4444-4444-8444-444444444444" \
 -H "Authorization: Bearer $TOKEN"

ResponseCopy Anchor Link

{ "success": true }

ErrorsCopy Anchor Link

• 400 SSH monitor public ID (UUID) required
• 401 Unauthorized
• 403 Forbidden (readonlyMayNotDelete for a read-only caller, managed_by_organization for a managed resource without canEditManaged)
• 404 Not found

PermissionsCopy Anchor Link

Closed to the readonly role. A read-only login deletes no monitor, whatever its ownership class, and neither does an API token it issued: a token inherits the role of the user who created it. Editing a self_service monitor stays open to that role.

A customer-scoped caller is bound by ownership class on top of that: a managed monitor is refused with managed_by_organization unless its customer carries canEditManaged.