Delete IMAP/POP Monitor

DELETE /api/imap-pop-monitors/:imapPopMonitorPublicId

AuthenticationCopy Anchor Link

Requires a valid session.

• Header: Authorization: Bearer <token>

ParametersCopy Anchor Link

• imapPopMonitorPublicId (Path, required): IMAP/POP monitor public UUID.

ResponseCopy Anchor Link

{ "success": true }

ErrorsCopy Anchor Link

• 400 IMAP/POP monitor public ID (UUID) required
• 401 Unauthorized
• 403 Forbidden (e.g. readonly or global supporter)
• 404 IMAP/POP monitor 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.