Delete FTP Monitor

DELETE /api/ftp-monitors/:ftpMonitorPublicId

AuthenticationCopy Anchor Link

Authorization: Bearer <token>

ParametersCopy Anchor Link

• ftpMonitorPublicId (Path, required): FTP monitor public UUID.

Example (cURL)Copy Anchor Link

BASE_URL="https://uptimeify.io"
TOKEN="<your-api-token>"

curl -X DELETE \
 "$BASE_URL/api/ftp-monitors/55555555-5555-4555-8555-555555555555" \
 -H "Authorization: Bearer $TOKEN"

ResponseCopy Anchor Link

{ "success": true }

Common ErrorsCopy Anchor Link

• 401 Unauthorized if you are not authenticated
• 403 Forbidden if you do not have write access (e.g. global supporter or read-only)
• 404 FTP monitor not found if the monitor does not exist

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.