Discussions

This option does not appear to work when creating a domain currently. It does function when updating a existing domain. Are there any plans to enable this when creating a domain?

The only thing I can find is Update SMS Number Copy https://{server}/ns-api/v2/domains/{domain}/smsnumbers/{smsnumber}

I was looking through the v2 API docs and noticed that there are few definitions for fields that don't make sense. On the Config/Configuration Definitions section, every time the field "config-def-allow-reseller-access" or "config-def-allow-hostname" is mentioned, the description for the field seems to be related to timeframes, not config definitions. It looks like the same description was copy and pasted for both "config-def-allow-hostname" and "config-def-allow-reseller-access." Just wanted to bring to your attention.

How are others in the community handling messaging compliance requirements, specifically with regards to the opt-out message and adding STOP responders to the outbound blocking list? Is the only option manual addition and management by the user/customer or has someone put together a creative solution?

The UI Parameter 'PORTAL_EXTRA_JS' allows for custom JavaScript to be inserted into the portal. Several elegant solutions including prompt-voice has successfully used this to integrate their third party application directly into the Manager Portal.

How i can get my domain NSD bearer token without NSR token thru API call

How to use api v2 to set CUSTOM agent states please ?

We just hit a huge roadblock when using v2. We found a few GET requests that return a max of 100 records. This happens in the docs as well as when I hit the API via script or Postman. There is no indication that more records exist, so records are going unnoticed which greatly impact our processes. Is there a hidden parameter we need to set to get all/unlimited records back? For example, we have 429 dial rules for our domain, but the GET dial rules in a dial plan call only returns 100 of them. When using the same call but in v1, all 429 records were returned. As a precaution, we are assuming that all GET requests have this limit, so we can't use v2 until this gets sorted out. Can we get this looked into ASAP?

When trying to add a new dial rule into a dial plan via the docs, I found that the field "dail-rule-matching-to-uri" is mispelled. I started looking through all of the calls under the Dialrule category and found that it's mispelled in the other calls too. Can we get this fixed?