Message Structure

Learn how SOAP messages must be structured when using the pmsXchange API, including formatting, headers, and authentication requirements.

Soap Message Structure

All SOAP messages (Requests/Responses) exchanged between SiteMinder and the PMS/RMS must:

  • Adhere to the SOAP message format.

  • Encapsulate the OTA message within the SOAP Body.

  • Requests must include a SOAP Security Header for authentication purposes.

  • Responses must be returned in a SOAP envelope. However, the SOAP Header should be empty.

Version

pmsXchange is using SOAP 1.1

Name
Value

Content-Type

text/xml; charset=utf-8

Authorization

Basic <credentials>

Security Header

The Security Header structure conveys authentication information.

<wsse:Security soap:mustUnderstand="1"	
	xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
	xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
	<wsse:UsernameToken>
		<wsse:Username>USERNAME</wsse:Username>
		<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">SECRET</wsse:Password>
	</wsse:UsernameToken>
</wsse:Security>

The only acceptable value for the Password @Type attribute is http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText. Plain text passwords are acceptable as all communication is done over encrypted HTTP (HTTPS).

Credentials

SiteMinder will provide partners with a single username and password to be used for authentication. These credentials will be global for all hotels using the connection.

Example

Last updated

Was this helpful?