Getting Started
Get started with the pmsXchange API and begin your integration with SiteMinder.
Test Environment
Each PMS connecting to the SiteMinder platform via pmsXchange API will be provided with an interactive test account to establish a basic connection.
SiteMinder will provide the
endpoint
,username
,password
, andRequestorID
(PMS code), enabling the PMS to retrieve rooms and rates, push availability, restrictions, and rate updates, and connect to the reservation service.SiteMinder will provide a
HotelCode
for the test hotel.SiteMinder will provide a reservation tool to test the reservation service.
Test Extranet
The connecting PMS will get access to a test hotel on the SiteMinder Platform to confirm that the availability, restrictions and rates pushed from their system are processed correctly. The platform will also show the reservations created and the delivery status to the PMS.
Test Web Service
Test Web Service URL: https://tpi-pmsx.preprod.siteminderlabs.com/webservices/{RequestorID}
We provide multiple WSDL variations to accommodate different technology stacks:
Inlined WSDL (Recommended for .NET): https://tpi-pmsx.preprod.siteminderlabs.com/webservices/{RequestorID}/pmsxchange_flat.wsdl
Payment Transaction Record WSDLs
Inlined WSDL (Recommended for .NET): https://tpi-pmsx.preprod.siteminderlabs.com/webservices/{RequestorID}/pmsxchange_pms_payments_flat.wsdl
For .NET clients, we recommend using the inlined WSDL, as the standard version may cause issues with .NET proxy generators (e.g., wsdl.exe or svcutil.exe) due to OTA specifications.
Ping Request
The connecting PMS can send an OTA_PingRQ
request to verify that the test web service is operational and that a connection can be established successfully. The Ping request only validates the endpoint’s availability; it does not verify credentials.
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:UsernameToken>
<wsse:Username>USERNAME</wsse:Username>
<wsse:Password>PASSWORD</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<OTA_PingRQ xmlns="http://www.opentravel.org/OTA/2003/05" EchoToken="ed8835ff-6198-4f38-b589-3058397f677c" TimeStamp="2024-07-06T15:27:41+00:00" Version="1">
<EchoData>Hello World</EchoData>
</OTA_PingRQ>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Your First API
The Rooms and Rates is the first step in your SiteMinder integration. You will need to connect to our Rooms and Rates
service to allow your system to request room types and rate plans from SiteMinder for testing. Once this step is completed, we'll create a test account for you to access the SiteMinder platform.
Postman Collection
To assist with automating your testing, please fork SiteMinder's PMS Postman Collection, where you will see various request scenarios, as well as the detailed breakdown of the Reservation Certification Scenarios.
Step 1 - Fork SiteMinder's PMS Postman Collection and pmsx-api environment.
Step 2 - Update the PMS environment with your specific details.
Step 3 - Select Run Collections
.
Step 4 - After running the collection, a summary will display showing which scenarios passed or failed.
Step 5 - Click View Results
to see more details on each test, including the Request
sent and the Response
received.
For more details on using Postman, see the article Test your API using the Collection Runner.
SiteMinder provides a test account for use during the active development phase. This account is intended solely for development purposes and should not be used for ongoing testing or demonstrations. Access to the test account will be disabled upon completion of the SiteMinder certification.
Help Centre
Last updated
Was this helpful?