"telegramEnabled" remains always true, even when trying to disable Telegram notifications (api)

[LetsGoDude]

Description

Hi Overseerr Team,

I've noticed that regardless of how I send the telegramEnabled field in the POST /api/v1/user/<ID>/settings/notifications endpoint, Overseerr always retains telegramEnabled: true.
Setting it to false in the request body does not actually disable Telegram notifications. Instead notificationTypes.telegram is set to 0 (e.g., "telegram": 0)—at which point telegramEnabled still remains true, even though notifications are effectively disabled.

Not a big problem, but it just doesn't behave as you would expect.
I bypassed it by setting ‘notificationTypes’: {
‘telegram": 3661 } to activate and 0 to deactivate.

Version

1.33.2

Steps to Reproduce

Make a POST request to /api/v1/user/<OVERSEERR_USER_ID>/settings/notifications with:

# Nothing applies here. Notification Types all remain deactivated.

{
  "notificationTypes": {
    "telegramEnabled": true
  },
  "telegramSendSilently": true
}

{
  "notificationTypes": {
    "telegramEnabled": false
  },
  "telegramSendSilently": true
}

# Notification types are all deactivated, but ‘telegramEnabled’ remains true.

Screenshots

Logs

Platform

desktop

Device

x86 PC AMD

Operating System

ubuntu 24.04 desktop

Browser

Firefox / Chrome

Additional Context

No response

Code of Conduct

• I agree to follow Overseerr's Code of Conduct