Fetching a user's notifications preferences via the API

Hi PeerTube community,

I’m developing a mobile app for our institutional PeerTube instance and running into an issue with the notification settings API. I’m hoping someone can clarify the current state of this functionality.

Current Situation:

  • PUT /users/me/notification-settings works perfectly - I can update notification settings successfully (returns 204)
  • GET /users/me/notification-settings returns 400 Bad Request with empty error message

What I’ve Tried:

  • Different headers (Accept: application/json, minimal headers, etc.)
  • Alternative endpoint paths (/users/me/preferences/notifications, /users/me/settings/notifications, /users/me/notifications/settings)
  • All return 400 Bad Request

Questions:

  1. Is the GET endpoint supposed to work? The OpenAPI spec suggests both GET and PUT should be available
  2. What PeerTube version added GET support? Could this be a version compatibility issue?
  3. Are there any server configuration flags that might disable the GET endpoint while keeping PUT enabled?
  4. Is there an alternative API endpoint to retrieve current notification preferences?

Why This Matters:
Without the ability to read current settings, mobile/desktop apps can’t:

  • Sync settings across devices
  • Show current preferences to users
  • Stay in sync with web interface changes
  • Provide a consistent user experience

Hi,

This is a documentation issue. There’s no GET endpoint on that path.

To retrieve notification settings, just fetch the user info using GET /users/me. I’ll update the documentation to remove this endpoint and add the notificationSettings of the GET /users/meendpoint

Thanks for the reply Chocobozzz -
I’m looking at the documentation for the GET /users/me endpoint, and it doesn’t appear to contain the user’s notification settings in the response. Is that a documentation issue as well, or am I reading it incorrectly?

Ahh - I just ran a test on my PeerTube instance, and the /users/me endpoint DOES provide the notification settings - it’s just not in the docs!