...

This feature request was added to the roadmap (expected to get attention during Q4). Issue tracker: UI-3384

Relevant API doc is here. As far as I can tell, this feature is not on our roadmap, but since the Faxes app is open source (repo), anyone would be more than welcome to create a PR implementing this feature.

Roger that, your complaint was reported to our backend team and a fix in the form of a system config flag to control this feature will come around soon (I didn't get a hard time line though).

Correct, this toggle only impacts the current account you are logged into.

I believe one way to disable such notifications would be to turn the threshold alerts off: Control Center > Usage Charges > Add Credit > Threshold Alerts > toggle "Turn on Threshold Alerts" off

The Provisioner and Call Center apps are both paid apps. That said, you do not inherently need to use 2600Hz's hosted platform to buy those apps; I encourage your to contact sales@2600hz.com for more information.

In order to add spare numbers to an account, you need to buy them. To do so, just click the `Buy` button corresponding to the account to which you want to add spare numbers to, and pick the number type and area code. Once that's done, the numbers will be listed as spare numbers under the account you chose when buying them.

Currently, it is not possible to achieve this result in Operator Console. I created a ticket to acknowledge your feature request and keep track of it.

Hi, Over the years, I have been building a Postman collection of Kazoo APIs that I use for testing purposes when building Monster applications. It seems like people would be interested in such a collection, and because we would rather not have to work on a Developer app that would be inferior in every way, I just created a quick tutorial on how to import that collection and set up Postman to make it easy to use and automate authentication (specifically, storing the authentication token and reusing it for every request). Keep in mind that this collection is extensive but not 100% complete and some PUT/POST endpoints are missing. Link to the tutorial

Hi @Tuly, To define the name of a callfow, you will have to create a `name` property at the root level of your callfow object. In your case, it would look like this: { "data": { "name": "Tuly's new callfow", "flow": { ... }, "numbers": [ "*1000" ], "patterns": [] } } Also, unless you are updating an existing callfow, you do not have to add the `id` property, as it will be generated automatically upon creation of your callfow.