Testing and Certification
Last updated
Was this helpful?
Last updated
Was this helpful?
Once you have completed development, use this guide independently as a testing checklist and a self-certification tool to help you verify that all required capabilities for integration have been thoroughly tested.
Once ready, the Partner Integrations team will review your readiness. Upon approval, we will prepare your account and confirm when you can proceed with the formal certification process.
To use this guide, ensure that you have access to our test Platform and that it's configured and mapped to your PMS. Additionally, you must have access to our test endpoint to send requests.
This guide provides a series of scenarios to test all available pmsXchange API capabilities. Only Availability and Reservation (Initial Delivery) are mandatory; the other capabilities are strongly recommended. If you do not support any of these optional capabilities, skip it and proceed to the next test scenario.
Once you have completed all test scenarios, you will be asked to fill out a form providing all the necessary information to finalize the certification.
To assist with automating your testing please fork SiteMinder's , where you will see various request scenarios, as well as the detailed breakdown of the Reservation Certification Scenarios.
Step 1 - Fork SiteMinder's and .
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 .
Check that you received a Success response from SiteMinder
Check SiteMinder Platform -> Distribution -> Inventory Grid if the updates have been applied.
This scenario tests updates where only specific data points, like a single rate change or availability adjustment made in the PMS, are sent for a short period, verifying the PMS ability to push delta data updates efficiently and accurately.
To complete this scenario, first select any future month within the next year. Then, for each specified day in the table (e.g., Day 1, Day 2, Day 5), apply the changes using the corresponding dates within that chosen month. For example, if you select March, use March 1 for Day 1, March 2 for Day 2, and March 5 for Day 5.
Set availability for the following room type and date.
Room A
Day 1
6
Room B
Day 5 to Day 10
10
Set restrictions for the following room rates and dates.
Room A
Rate 2
Day 3 to Day 7
Enable Stop Sell
Room A
Rate 2
Day 5
Disable Stop Sell
Room A
Rate 2
Day 4
Enable CTA
Room A
Rate 2
Day 7
Enable CTD
Room A
Rate 2
Day 1 to Day 28
Min. Stay to 2
Room A
Rate 2
Day 1 to Day 28
Max. Stay to 7
Set rates for the following room rates and dates.
Room A
Rate 2
Day 15 to Day 17
200
Room A
Rate 2
Day 18
300
Room A
Rate 2
Day 20 to Day 21
350
Room A
Guest 1
Day 1 to Day 15
150
Guest 2
200
Guest 3
250
Guest 4
300
Guest 5
350
Go to the Basic tab and click Generate under the Two Different RoomType - Rateplan, 1 night section.
Verify the 2 room types are different.
Date Range: Select any 1 night. Ex: 07/04/2023 - 07/04/2023 is the 1 stay night. This is not the check-in and check-out dates. Keep the same dates for both.
Click Send
Go to the Basic tab and click Generate under the Two Same RoomType - Rateplan, 1 night section.
Verify the 2 room types are same.
Date Range: Select any 1 night. Ex: 07/04/2023 - 07/04/2023 is the 1 stay night. This is not the check-in and check-out dates. Keep the same dates for both.
Click Send
Go to Sent Scenarios on the left nav bar.
Find the reservationID and click Modify
Delete one of the room types or Change stay dates.
Click Send
Same as modifications, go back to Sent scenarios and Cancel the test reservations. Using the OTA_HotelAvailNotifRQ, the PMS sends back the affected 'Availability' change/increase.
Go to Sent Scenarios on the left nav bar.
Find the reservationID and click Modify
Click Cancel Reservation
Click Send
If you are using this guide as a testing checklist and are now ready to begin certification, please contact the Partner Integrations team to confirm your readiness. If you are already in the certification process, complete the form provided via email, ensuring that all required information is accurately included for final review.
From the PMS, send a small full flush of all mapped room types' availability, rates and restrictions. You can do a flush of 30, 60 or 90 days. This test is to ensure your PMS is bundling dates and optimizing messages as per our requirements.
You can use our PMS Toolkit and Direct Booking engine URL to create test reservations, modifications and cancellations and check the Reservations API flow is working. Refer to the section for further details. The following are common reservation types and modifications that you will receive from various booking sources (OTA's). Access the PMS Toolkit here:
For security reasons, always use test credit card details and never real ones when testing reservations. Refer to .
This scenario tests your system’s ability to accept Multi RoomStay reservations with two or more rooms booked for the same date range and/or consecutive days within the RoomStays element.
From the :
For modifications, you can create any reservation from , go back to Sent scenarios and Modify the test reservations. You can change the stay dates or room type booked. Using the OTA_HotelAvailNotifRQ, the PMS sends back the affected 'Availability' change (increase or decrease) based on the modification type.
