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:
- Is the GET endpoint supposed to work? The OpenAPI spec suggests both GET and PUT should be available
- What PeerTube version added GET support? Could this be a version compatibility issue?
- Are there any server configuration flags that might disable the GET endpoint while keeping PUT enabled?
- 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