Testing and Certification
Last updated
Last updated
This guide serves as both a testing checklist and a self-certification tool to help you verify that all required capabilities for integration have been thoroughly tested. You can use this guide independently for testing purposes, and once you’ve completed development and are confident in the results, 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 we have configured your booking channel’s endpoint to retrieve room rates and receive updates. Additionally, you must have access to our reservation endpoint to send reservation messages to us.
This guide provides a series of scenarios to test all available SiteConnect API capabilities. Only Availability
, Stop Sell
, Rates
, 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 necessary information to finalize the certification.
If your booking channel does not support non-mandatory functionalities such as any restrictions, inclusions, occupancy details, or extras/discounts, please inform us so we can exclude them from your test platform configuration.
For certification purposes we have created two basic room types and two basic rate plans that are ready to be mapped to your booking channel. Please create in your system the same room rates combination to start the certification.
If your booking channel doesn't support multiple room types and/or multiple rate plans, create them as possible and let us know.
A request is sent to your system each time you access the Room Rates Mapping section of your booking channel in your test Platform. You can trigger a new request by clicking the refresh arrow.
Ensure that your system provides a Success
response, displaying all available rooms and rates from your end.
Confirm that channel room rate names are accurate (e.g., Channel Room A - Channel Rate 1).
Complete the mapping of the four rate plans created for certification, adding Occupancy Details
, Extra / Discounts
and Channel Inclusions
if supported.
Optional: Test Additional Details, including NO_RATES
, NO_AVAILABILITY
, and NO_UPDATES
.
To successfully complete this scenario, you must have retrieved all room rates created on your booking channel. The room rates required for certification must have been mapped on your test Platform.
Using the Bulk Update tool, set up Availability, Restrictions, and Rates for the update period configured for your booking channel (e.g., 750 days). These changes will push Availability, Restrictions, and Rates updates to your system, and we expect successful responses. See some examples below:
Set availability for both room types starting from today for the update period supported by your booking channel (e.g., 750 days).
Room A
Full Update Period
10
Room B
Full Update Period
5
Set rates for all four room rates starting from today, covering the update period supported by your booking channel (e.g., 750 days).
Room A
Rate 1
Full Update Period
300
Room A
Rate 2
Full Update Period
250
Room B
Rate 1
Full Update Period
400
Room B
Rate 2
Full Update Period
350
The values above represent the base amount for each rate. Additional amounts are included in the request if Occupancy Details
and Extra / Discounts
are configured during the mapping setup.
Set stop sell for all four room rates starting from today, covering the update period supported by your booking channel (e.g., 750 days).
Room A
Rate 1
Full Update Period
Enabled
Room A
Rate 2
Full Update Period
Disabled
Room B
Rate 1
Full Update Period
Enabled
Room B
Rate 2
Full Update Period
Disabled
Set close to arrival for all four room rates starting from today, covering the update period supported by your booking channel (e.g., 750 days).
Room A
Rate 1
Full Update Period
Enabled
Room A
Rate 2
Full Update Period
Disabled
Room B
Rate 1
Full Update Period
Enabled
Room B
Rate 2
Full Update Period
Disabled
Set close to departure for all four room rates starting from today, covering the update period supported by your booking channel (e.g., 750 days).
Room A
Rate 1
Full Update Period
Enabled
Room A
Rate 2
Full Update Period
Disabled
Room B
Rate 1
Full Update Period
Enabled
Room B
Rate 2
Full Update Period
Disabled
Set minimum stay for all four room rates starting from today, covering the update period supported by your booking channel (e.g., 750 days).
Room A
Rate 1
Full Update Period
1
Room A
Rate 2
Full Update Period
7
Room B
Rate 1
Full Update Period
1
Room B
Rate 2
Full Update Period
7
Set maximum stay for all four room rates starting from today, covering the update period supported by your booking channel (e.g., 750 days).
Room A
Rate 1
Full Update Period
7
Room A
Rate 2
Full Update Period
30
Room B
Rate 1
Full Update Period
7
Room B
Rate 2
Full Update Period
30
Min. Stay and Max. Stay are by default configured on Arrival (SetMinLOS
and SetMaxLOS
). To switch to Min. Stay Through and Max. Stay Through (SetForwardMinStay
and SetForwardMaxStay
) set Use stay through to Yes
in your Channel Settings
.
Use the View by
and Select a data type to display
options to easily review changes made on your test platform.
To successfully complete this scenario, your booking channel must have accepted and processed the Availability, Restrictions, and Rates updates sent. Your system must display the same data as your test Platform.
This scenario tests updates where only specific data points, like a single rate change or availability adjustment, are sent for a short period, verifying the system’s ability to handle minimal 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
0
Set restrictions for the following room rates and dates.
Room A
Rate 2
Day 3
Enable 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
If your booking channel supports Occupancy Details
, Extra / Discounts
and Channel Inclusions
, ensure that the received rate data is processed accordingly. Below are the expected outcomes for both pricing models: Per Day Pricing
and Occupancy Based Pricing
using the rate update for the Room A - Rate 2
on the Day 18
for 300
as an example:
To successfully complete this scenario, your booking channel must have accepted and processed the Availability, Restrictions, and Rates updates sent. Your system must display the same data as your test Platform.
Based on the data pushed to your booking channel during the Bulk Data Update
and Targeted Data Update
, you are required to complete the following test scenarios. All successfully created bookings must contain the maximum amount of data your booking channel can handle, including guest and customer details, services, guarantee and deposit information, credit card or virtual credit card information, and more. Any data not received will be deemed as not supported by your booking channel.
Refer to the Reservations section for further details.
For security reasons, always use test credit card details and never real ones when testing reservations. Refer to Test Credit Cards.
This scenario tests your system’s ability to prevent bookings that don’t meet availability or restriction criteria, verifying that it accurately enforces rules to block reservations when availability or restrictions don’t permit them.
Attempt 1
Room A
Rate 2
Day 1
Day 3
Availability
Attempt 2
Room A
Rate 2
Day 2
Day 4
Stop Sell
Attempt 3
Room A
Rate 2
Day 4
Day 6
CTA
Attempt 4
Room A
Rate 2
Day 5
Day 7
CTD
Attempt 5
Room A
Rate 2
Day 8
Day 9
Min. Stay
Attempt 6
Room A
Rate 2
Day 10
Day 14
Max. Stay
This scenario tests your system’s ability to provide a rate breakdown within the RoomRates
element. Create the following test reservations:
Booking 01
Room A
Rate 2
Day 15
Day 18
Same Value per Night
Booking 02
Room A
Rate 2
Day 17
Day 20
Different Value per Night
Booking 03
Room A
Rate 2
Day 19
Day 22
Combined
If your booking channel doesn't provide Daily Rates
, still create the reservations with the requested room type, rate plan, check in and check out dates.
This scenario tests your system’s ability to provide reservations with two or more rooms for the same date range and/or consecutive days within the RoomStays
element. Create the following test reservations:
Booking 04
Room A
Rate 2
Day 22
Day 28
Room B
Rate 2
Day 22
Day 28
Booking 05
Room A
Rate 2
Day 22
Day 25
Room B
Rate 2
Day 25
Day 28
If your booking channel doesn't support Multi Room
reservations, ignore the reservation Booking 04, but still create the reservations Booking 05 using the same room type.
Modify the following test reservations.
Booking 01
Remove one night
New check out Day 17
Booking 02
Add one night
New check out Day 21
Booking 04
Remove Room B
Only Room A remains
Booking 05
Change Room A to B
Both are Room B
Cancel the following test reservations.
Booking 01
Cancel
Booking 03
Cancel
Booking 05
Cancel
To successfully complete this scenario, you must have created and sent reservation requests for each test: Daily Rates, Multi Rooms, Modifications, and Cancellations. Our system must display reservation data consistent with your booking channel.
To assist you in testing the Error Handling, use the Postman collection SiteConnect - Error Handling
. Follow the steps below to begin your testing process.
Step 1 - If you haven't already, fork the relevant collection from https://www.postman.com/siteminder-apis/channels/overview
Step 2 - Update the SiteConnect
environment with your specific details.
Step 3 - Select Run Collection
.
Step 4 - Choose the scenarios you need to run based on whether you’re testing PDP or OBP. Also, set a Delay
of 2000 ms, enable Persist responses for a session
, and then select Run SiteConnect - Error Handling
.
Step 5 - After running the collection, a summary will display showing which scenarios passed or failed.
Step 6 - Click View Results
to see more details on each individual test, including the Request
sent and the Response
received.
For more details on using Postman, see the articles Test your API using the Collection Runner.
To successfully complete this scenario, you must execute each error handling test in the provided Postman collection. Ensure that your system correctly identifies and responds to errors as specified, with responses consistent with the expected descriptions.
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.