PMS Integration Partners
Sandbox Runner
Run the nine sandbox steps in order right in your browser, see the real response to each request, then compare against the seven certification checks. Everything happens in the sandbox's separate test database, with no data exchange with production.
No sandbox account yet? Submit the PMS partner application. Your account is issued immediately and filled in on this page automatically (stored only in this browser tab).
Sandbox account
The nine steps
1Retrieve room types and rate plans (OTA_HotelProduct)Not run
2Push daily rates (OTA_HotelRateAmountNotif)Not run
3Push availability (OTA_HotelAvailNotif)Not run
4Channel quote (POST /api/mp/quote)Not run
5Channel hold, inventory taken immediately (POST /api/mp/bookings, hold:true)Not run
6Pull: the held booking is already visible (OTA_HotelResNotif)Not run
7Confirm after payment (POST /api/mp/bookings/{bookingKey}/confirm)Not run
8Cancel and restore inventory (POST /api/mp/bookings/{bookingKey}/cancel)Not run
9Pull again: the same booking is now CancelNot run
The seven certification checks
Evaluated by the sandbox server from the calls it actually received, so running your own code updates it too. It is queried automatically after the nine steps finish.
1Retrieve room types and rate plans (OTA_HotelProduct)Not checked
2Push daily rates (OTA_HotelRateAmountNotif)Not checked
3Push availability and open/close (OTA_HotelAvailNotif)Not checked
4Channel hold takes inventory (hold:true)Not checked
5Hold confirmed (/confirm)Not checked
6Cancellation restores inventory (/cancel or hold expiry)Not checked
7Reservation pull after a booking (OTA_HotelResNotif)Not checked
Requests and responses
Steps 4, 5, 7 and 8 simulate a selling channel so you can see how a booking appears in your reservation pull without waiting for real orders. In a production integration the PMS only implements steps 1, 2, 3, 6 and 9. See the developer specification for every field.