bitsofinfo

Great, and what about the GUI issue w/ the radio buttons vs checkboxes. The GUI does not properly reflect the actual regions bound via the API, and if you hit modify you change it to a single region which is not the intent.

also FYI, I've already coded quite a against whats documented on your 3.1 docs. Please don't break it The issues above still should be addressed IMHO

Here are some additional issues 1. When creating/updating a check there is no way to specify the "check importance" of "low" or "high". (actually you can but its NOT documented, pass severity_level = LOW|HIGH) 2. Creating/updating checks takes comma delimited lists of userids, integrationids, teamids etc... yet the API…

Any ETA on this? Note that the documentation for 3.1 as it currently stands, w/ the url-encoded format POST/PUT for managing "checks" appears to work so I'm likely just going to code to this published documented spec. I assume that if you change it back to the originally published JSON contract, you would then release it…

Unfortunately its still confusing and not clear how you specify the documented props especially now that its reverted to url encoded format

Just was about to go to tweet you guys as I was concerned nobody was paying attention. Thanks for the reply Glad to hear I wasn't going nuts and that its being remedied, I contacted support and they were trial/erring through the process as well. It appears completely non-functional. FYI the swagger docs even for 2.1 (as of…