SOA POST API support with content type JASON in SMS Gateway Integration

[Jay Tiwari]

Currently customers SOA server accepts the data in JSON format and below is the sample format that their server can accept :

POST https://<<IP>>:<<PORT>>/ENS/v1/SMS HTTP/1.1
Accept-Encoding: gzip,deflate [Required, constant]
APIKEY: XYZ12345 [Required, constant]
Content-Type: application/json [Required, constant]
Content-Length:
Host: <<IP>>:<<PORT>>
Connection: Keep-Alive
User-Agent: Apache-HttpClient/4.1.1 (java 1.5)
{
  "SMS":{
    "ReqHeader":{
      "RqUuid":"XYZ123", [Required, dynamic]
      "ClientId":"XYX", [Required, constant]
      "ClientCountry":"SG", [Required, constant]
      "TraxDateTime":"2016-10-19T15:29:32" [Required, dynamic]
    },
    "ReqBody":{ [TBD]
      "Field1":"Value 1",
       "Field2":"Value 2"
    }
  }
Now i have following questions:

1.Is above mentioned header is supported in Administration--System--Setting--SMS Gatway--Provider API page.

2. is above mentioned JSON format supported under “HTTP POST data content type” in Administration--System--Setting--SMS Gatway--Provider API page.

3. If the above is supported, what’s the format the data is sent out in JSON

Many Thanks,

 

1. s specifying the format as JSON under “HTTP POST data content type” supported.
2. If the above is supported, what’s the format the data is sent out in JSON
3. s specifying the format as JSON under “HTTP POST data content type” supported.
4. If the above is supported, what’s the format the data is sent out in JSON

[Jason Kunst · Accepted solution]

I am also working on this internally 

[Jason Kunst]

i am still checking internally on this with the developers. you can also open a tac case to investigate with vendor to see if any workaround. What is the provider name? can they give us a sample account and contact info to work together? This can all be coordinated through TAC. Please keep us updated as well.