SMSGateway

SendSmsRequest

The following routes are available for this service:
POST	/sendsms

**SendSmsRequest** Parameters:
Name	Parameter	Data Type	Required	Description
security	body	SecurityRequestDto	No
notify	body	SmsBodyDto	No

**SecurityRequestDto** Parameters:
Name	Parameter	Data Type	Required
partner_id	form	string	No
time	form	string	No
hash	form	string	No

**SmsBodyDto** Parameters:
Name	Parameter	Data Type	Required
service_id	form	string	No
number	form	string	No
carrier	form	string	No
message	form	string	No
encode	form	int	No
url	form	string	No
test	form	int	No
mask	form	string	No
xtraparams	form	Dictionary<string, string>	No

**ResponseSmsDto** Parameters:
Name	Parameter	Data Type	Required	Description
result	form	ResultResponseDto	No

**ResultResponseDto** Parameters:
Name	Parameter	Data Type	Required
code	form	string	No
message	form	string	No
id	form	string	No

To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /sendsms HTTP/1.1 
Host: 67.208.218.153 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"notify":{"carrier":"String","encode":0,"mask":"String","message":"String","number":"String","service_id":"String","test":0,"url":"String","xtraparams":[{"Key":"String","Value":"String"}]},"security":{"hash":"String","partner_id":"String","time":"String"}}

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"result":{"code":"String","id":"String","message":"String"}}