Hi Jason,
I attach the data action, this is how I have configured it, it seems strange to me that it is from the configured authorization since it works well. It may be that they have to give us permissions in the /api/sms path?
For situations like this I would always suggest going back to something like postman to verify you can get the endpoint working, and then go from there.
If this is working in postman then you should check the troubleshooting guide.
web services tab -> custom action fails for unexpected reason
Hello, Inspecting the api request, it gives status error: CORS error and type: fetch has been blocked by CORS policy: Request header field countryid is not allowed by Access-Control-Allow-Headers in preflight response.
This is a client webservice problem, right? Thank you
Hello, I already solved it, it was a failure of the client's web service, on the other hand now I find that the "&" character in genesys gives me an error, is there another way to analyze this data?