...
The payload, which is based on specific OTA 2006B XML schemas, is the business or application content of the message that corresponds to the specific transaction being invoked. One payload per envelope is assumed.
Sample SOAP envelope
The following is an example of a SOAP envelope containing the HTNG header used for authentication:
Code Block | ||
---|---|---|
| ||
<?xml version="1.0" encoding="UTF-8" ?> <soap:Envelope xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> <soap:Header> <HTNGHeader xmlns="http://htng.org/1.1/Header/";> <From> <systemId="145124"> <Credential> <userName="partner"> <password="a1b2c3"/> </Credential> </From> <To> <systemId="Windsurfer"/> </To> <timestamp>date</timestamp> <echoToken /> <transactionId /> <action /> </HTNGHeader> </soap:Header> <soap:Body> </soap:Body> </soap:Envelope> |
SOAP Fault Handling [Errors]
If a SOAP error occurs during processing, the SOAP body must contain a SOAP Fault element. Note that the Fault element can only appear once in a SOAP message. Therefore, only the first error encountered is reported. An accompanying fault string attribute shall contain a detailed description of the specific error.
...