Send SMS using a SMS Gateway in Android with CURL command

[Ricardo.a4]

Hi!
I install a SMS Gateway in a phone with android.
If a use the CURL in command line, I can send the mensages perfectly.
I try to transform this to use in Foxpro, have no luck.
Anyone can do a magic and help me?
Thanks in advance

Commandline:
curl -X POST

http://192.168.10.57:8082

-H "Content-Type: application/json" -H "Authorization: f3e09bbd" -d "{"to": "+351987654321", "message": "Teste envio OK"}"

FoxPro:
_comando = 'curl -X POST

http://192.168.10.57:8082

-H "Content-Type: application/json" -H "Authorization: f3e09bbd" -d "{"to": "987654321", "message": "Teste envio OK"}"'
msg(_comando) ShellExecute(0,"post",_comando,"","",1)

 

[atlopes]

Ricardo,

You may try to invoke the gateway service using the WinHTTP class.

LOCAL HTTPService AS WinHttp.WinHttpRequest

m.HTTPService = CREATEOBJECT("WinHttp.WinHttpRequest.5.1")
m.HTTPService.SetRequestHeader("Content-Type", "application/json")
m.HTTPService.SetRequestHeader("Authorization", "f3e09bbd")

m.HTTPService.Open("Post", "[URL unfurl="true"]http://192.168.10.57:8082/",[/URL] .F.)

m.HTTPService.Send('{"to": "987654321", "message": "Teste envio OK"}')

 

[Chris Miller]

Hi Ricardo,

looking back at my answer in thread184-1813603

You just have to add 1 and 1 together, realizing that the CURL -H options are request headers (H):

LOCAL loRequest, lcPOSTRequestbody

TEXT TO lcPOSTRequestbody NOSHOW
{"to": "987654321", "message": "Teste envio OK"}
ENDTEXT

loRequest = CREATEOBJECT("microsoft.xmlhttp")
loRequest.open("POST","[URL unfurl="true"]https://smsgateway.me/api/v4/message/send")[/URL]
loRequest.setRequestHeader("Content-Type","application/json")
loRequest.setRequestHeader("Authorization","f3e09bbd")

loRequest.send(lcPOSTRequestbody)
DO WHILE loRequest.readyState<4
   Doevents
ENDDO

? loRequest.Responsetext

What does that give you as response text?
Also, what is the response text when you don't set the Authorization header?

Chriss

 

[Chris Miller]

Just by the way, you should never post real passwords or api keys or any such secrets.

So if that's real, refresh it, change it, as soon as possible, so the posted Authorization key becomes invalid.

Chriss