POST | /receiveresult |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
result | body | ResultSmsDto | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
uidTransaction | form | Guid | No | |
Msisdn | form | string | No | |
ShortCode | form | string | No | |
ResultCode | form | string | No | |
ResultDescription | form | string | No | |
Carrier | form | string | No | |
Message | form | string | No | |
Result | form | string | No | |
PartnerId | form | int | 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
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /receiveresult HTTP/1.1
Host: 67.208.218.153
Accept: application/json
Content-Type: application/json
Content-Length: length
{"result":{"Carrier":"String","Message":"String","Msisdn":"String","PartnerId":0,"Result":"String","ResultCode":"String","ResultDescription":"String","ShortCode":"String","uidTransaction":"00000000-0000-0000-0000-000000000000"}}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {}