Trying to set up a lightweight listener for conversation:updated events in a Node.js service using the Genesys Cloud Notification API. I’ve got the auth flow sorted, grabbing the bearer token and hitting the WebSocket endpoint wss://api.mypurecloud.com/api/v2/notifications. The connection sticks, but the event stream is flooding my logs with every single update across the org. I need to narrow it down to just the conversations associated with a specific user ID or a set of routing queues. I’ve tried sending a subscribe message with a filter object like { "filter": { "userId": "12345" } }, but the server just ignores it and keeps pushing the global stream.
I’ve checked the docs and they mention using the subscriptions endpoint to register filters, but that’s usually for the REST API polling approach. For WebSockets, the mechanism seems different. I’ve tried attaching the filter directly in the initial connection URL query params, but that breaks the handshake. The payload I’m sending looks like { "action": "subscribe", "filter": { "userId": "12345" } }, but I’m getting no confirmation message back, just more noise. Is there a specific JSON structure required for the subscribe payload to actually work, or do I have to parse the full stream on the client side? The retry logic in my code is kicking in because the memory usage is spiking. Any ideas on how to scope this down without writing a custom filter engine?