Support for Configuring SMS Sender Policy Using a JSON Body or CURL script

Idea ID 2785841

Support for Configuring SMS Sender Policy Using a JSON Body or CURL script

Currently when configuring the SMS Sender policy we only support submitting parameters in the http request URL. I was working with a customer that uses Avaya as their CpaaS provider and that system accepts submitting user parameters in a JSON body or CURL script. They consider submitting the parameters in the URL as a potential security risk. Would we be able to add in support for submitting the parameters via one of those methods in the future?
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.