Versions Compared

Version Old Version 3 New Version 4
Changes made by

Former user

Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Changed title to be easier searchable when looking for status codes

...

 Endpoints

We'll have two endpoints:

...

 

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://server.submission.mc5.smspl.com/">
   <soapenv:Header/>
   <soapenv:Body>
      <ser:status>
         <username>?</username>
         <password>?</password>
         <documentId>?</documentId>
      </ser:status>
   </soapenv:Body>
</soapenv:Envelope>

 

What information to return?

For the REST endpoint (JSON)

 

{
    "documentId": "4fbb6c371a88393bc47baf32",
    "recipient": "48660703691",
    "messageStatus": "10"
}

 

For the SOAP endpoint (XML):

 

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
   <soap:Body>
      <ns1:sendSingle2Response xmlns:ns1="http://server.submission.mc5.smspl.com/">
         <return>            
        <documentId>4fbb6cd21a88393bc47baf33</documentId>            
            <recipient>48660703691</recipient>
            <messageStatus>10</messageStatus>
         </return>
      </ns1:sendSingle2Response>
   </soap:Body>
</soap:Envelope>

 

Status codes

Basing on https://secure.mghhosting.com/wiki/download/attachments/12386334/SMSPL-SW-807-MCOR-0001+-+Web+Services+API+-+V1.06.2.pdf?version=1&modificationDate=1337252411000 and https://secure.mghhosting.com/wiki/display/MC4API/Web+Service+to+query+status. Some status codes are omitted as they can't (yet) occur in our application.

...

  • -110 (invalid xml): not possible? It would be an WS-framework error?
  • -211 (invalid service), -930 (status query timeout): N/A
  • -900 (service not available): ?
  • -940 (query too fast)

Submission URLs

To make the URLs uniform, the endpoints to submit messages will be:

...