Testing and Certification

Test your SMX integration and confirm readiness before going live with SiteMinder.

Use this guide to verify that all required integration capabilities are working correctly. Work through the scenarios independently, and when you're confident in your results, notify the Partner Integrations team. We'll review your readiness, prepare your account, and confirm when you can proceed to certification.

Instructions

This guide provides a series of scenarios to test all required integration capabilities for this API. Some capabilities may be optional — if a scenario does not apply to your integration, skip it and proceed to the next one. Work through each scenario using the resources provided in the Initial Setup section, and use the results to verify your integration is working correctly before requesting certification.

Once all scenarios pass, notify the Partner Integrations team. We will review your results, and if everything looks good, confirm when you can proceed to the formal certification process.

Initial Setup

Before working through the test scenarios, make sure the following are in place:

1. Postman collection — Download and import the SMX Postman collection.

2. Little Hotelier test account — You will need access to our test platform to run Reservation scenarios.

3. Active endpoint — Ensure your endpoint is active and ready to receive requests.

For Reservations, you will provide your own endpoint credentials. For Availability and Rates, retrieve your Bearer Token from the SMX Partner Portal. Make sure to replace all variables in the Postman collection before running the scenarios.

Test Scenarios

Reservations

Your application must accept all ResStatus values and respond with 200 OK:

Reserved, Waitlisted, Cancelled, No-show, In-house, Checked-Out.

- Error Handling

#	Scenario	Description
1	Invalid Username / Password	Validates error response when incorrect credentials are sent via SMX
2	Hotel Not Found for HotelCode	Validates error response when an invalid HotelCode is sent via SMX

- Minimum and Maximum Content

#	Scenario	Description
1	Minimum Content XML	A booking XML containing only the basic required fields handled by SMX
2	Maximum Content XML	A booking XML containing all possible fields handled by SMX

- Reservation Lifecycle (Modify)

#	Request	Description
1.1	Initial Booking	2-night stay
1.2	Move Dates	Check-in and check-out dates changed; same 2-night stay duration
1.3	Add Room	Same stay dates; additional room added
1.4	Remove Room	Same stay dates; additional room removed
1.5	Add Guests	Same stay dates; new guest added to the booking

- Reservation Lifecycle (Cancel)

#	Request	Description
2.1	Initial Booking	1-night stay
2.2	Add Rooms + Guests	Same stay dates; new room and guest added
2.3	Remove Rooms + Guests	Same stay dates; room and guest removed
2.4	Cancel	Full cancellation of the booking

- Services

#	Request	Description
3.1	Reservation with Services	New booking created with extra services attached

- Stay Status

#	Request	Description
4.1	Initial Booking	New booking created
4.2	Check-In	Same booking checked in
4.3	Check-Out	Same booking checked out

- Special Characters

#	Request	Description
5.1	Special Characters (No RoomID)	New booking with special characters across multiple fields

Your application must respond to every OTA_HotelResNotifRQ with a valid OTA_HotelResNotifRS. Return 200 for application-level errors with a clear error description; use 500/503 only for server-level failures.

If delivery fails, SMX retries every 30 seconds for up to 3 attempts before marking the reservation as failed. Review the Error Handling page for more details.

Availability and Rates

Rate limiting is not applied during testing. Limit requests to a maximum of 30 per minute per property.

- Publisher and Hotel

#	Scenario	Description
P1	GET publishers	Retrieve all publishers (PMSs) connected to your application
P2	GET hotels	Retrieve all hotels connected to the selected publisher and your application

- Room Types

#	Scenario	Description
RT1	GET RoomType by Hotel	List all room types for a specific hotel and publisher
RT2	GET RoomType by Room Code	Repeat for each room type code. Note: some fields are optional and may not be returned by all PMSs

- Rate Plans

#	Scenario	Description
RP1	GET RatePlans by Hotel	List all rate plans for a specific hotel and publisher
RP2	GET RatePlans by Rate Plan Code	Repeat for each rate plan code. Note: some fields are optional
RP3	GET Rates by Rate Plan Code	Repeat for each rate plan: once for current date, once for a future date
RP4	GET Rates by Rate Plan Code NumberOfDays	Repeat for each rate plan from current date with a range of 30, covering 1 full year

- Availability and Restrictions

#	Scenario	Description
AV1	GET Availability by Hotel / Room Type	Repeat for multiple dates and each room type code
AV2	GET Availability by Hotel / Room Type NumberOfDays	Repeat from current date to cover 1 full year; repeat for each room type code
AV3	GET Availability by Hotel / Rate	Repeat for multiple dates and each rate plan code
AV4	GET Availability by Hotel / Rate NumberOfDays	Repeat from current date to cover 1 full year; repeat for each rate plan code

---

Final Steps

Once all scenarios have passed, notify the Partner Integrations team. We will review your results and confirm when you can proceed to certification. If any issues are identified during the review, we will reach out to you directly to resolve them before moving forward.

Still have questions?

Use the Ask button at the top of the page to chat with our AI assistant — it can help you navigate the guide, understand requirements, and troubleshoot issues.

If you need more support, visit Integration Support.