How to avoid notification when posting to hipchat via apiv2?

[Ian Brown]

I'm using the 'Send Room Notificaiton' api (https://www.hipchat.com/docs/apiv2/method/send_room_notification) to send a message from an automated process to a dedicated hipchat room. I used to do this with v1 of the api and have recently moved to v2.

The problem is that whenever a post is sent, the hipchat app notifies the user via a toaster pop-up and a flashing icon in the task bar. With V1 this did not happen. I have set the notify parameter explicitly to false in the request in addition to omitting it (the default should be false) - it makes no difference.

This is problematic because the service posts an update every 5 minutes and so the hipchat app is always flashing and you so you miss notifications from real people. Is this a bug? Is there a workaround? Can I disable all notifications for this room only (the server posts to a dedicated room).

This looks like a regression from v1 to v2 of the hipchat API.

As an aside, I also tried using the Send Message call as logged in user and it has the same effect of always notifying.

[rbergman]

Try adding "notify: false" to the post body of the room notification.

[Ian Brown]

Hi Bob, yes I tried that originally. Made no difference.

[Anatoli]

Ian, I have just tested it and it worked for me. Might be a client problem? What client do you use (I tried Mac client)?

[Ian Brown]

I'm using the windows native client on windows 10 and 8.1. It could be a client issue as the phone client is okay ... but the old method (using API v1) works fine with the same windows client. Has there been any thought to making the client open source / source available as we could then at least hack a local copy to do the right thing?

[rbergman]

You might be interested to know that we have a new Windows client in closed beta now! Please see the following links for more information: https://help.hipchat.com/forums/138883-suggestions-ideas/suggestions/6800693-windows-ui-update http://goo.gl/forms/lYGPNImciH

[Ian Brown]

Thanks, I've signed up. Would be interested to know if anyone can confirm this to be an issue with the current windows client though. I guess it is because it looks fine on my iphone.